Project

Profile

Help

Issue #8460

As a developer, `pstop` and `pstart` only work with two workers

Added by bmbouter 7 months ago. Updated 7 months ago.

Status:
CLOSED - WORKSFORME
Priority:
Normal
Assignee:
-
Category:
Installer - Moved to GitHub issues
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

In my dev system I can use the ansible variable pulp_workers: 10 to start ten workers instead of the default two.

On that system when I run pstop or pstart I see that performs:

systemctl stop pulpcore-content pulpcore-worker@1 pulpcore-worker@2 pulpcore-resource-manager pulpcore-api

What I expected that to perform was to start and stop all 10 workers, but it's hard coded to two.

History

#1 Updated by bmbouter 7 months ago

As a workaround I've used:

sudo systemctl stop pulpcore-content pulpcore-worker@{1..10} pulpcore-resource-manager pulpcore-api
sudo systemctl start pulpcore-content pulpcore-worker@{1..10} pulpcore-resource-manager pulpcore-api

#2 Updated by fao89 7 months ago

#3 Updated by bmbouter 7 months ago

When I experienced this I actually ran the installer with pulp_workers: 2 and then reran it with pulp_workers: 10. So I think it may be handled correctly the first time, but not on the rerun.

#4 Updated by bmbouter 7 months ago

  • Status changed from NEW to CLOSED - WORKSFORME

The issue I had was that my TTY's were holding onto the old bashrc files. When I closed my TTY before rerunning the installer it worked perfectly. Thanks @mikedep333 for suggesting this on IRC.

Please register to edit this issue

Also available in: Atom PDF