Issue #8460
closed
As a developer, `pstop` and `pstart` only work with two workers
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.
Updated by bmbouter about 3 years 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
Updated by fao89 about 3 years ago
Our code was supposed to handle it: https://github.com/pulp/pulp_installer/blob/master/roles/pulp_devel/templates/alias.bashrc.j2#L4
I'll debug it tomorrow
Updated by bmbouter about 3 years 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.
Updated by bmbouter about 3 years 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.
.