Story #2469
closed
Story #2186: As a user, pulp-manage-db refuses to run if other pulp processes are running
As an user, I should be able to specify an option to pulp-manage-db to assume yes for the running workers question
0%
Description
It would be great to have an option (possible --force or --yes) for pulp-manage-db that makes it assume yes for all questions (currently only the "There are still running workers, continuing could corrupt your Pulp installation. Are you sure you wish to continue? (y/N)").
This will help run pulp-manage-db from within a script which will help automating the upgrade process, for example.
Updated by elyezer about 8 years ago
- Tracker changed from Issue to Story
- % Done set to 0
Updated by bmbouter about 8 years ago
Rather than position the name of the option about forcing or answering a yes/no quesiton, we could make the option disable the check altogether. Specifically I recommend naming it --ignore-running-workers. This allows us to reserve a "force" language for something that actually need to be forced and also allows us to ask yes/no questions without having this new option be at all related to that.
Also this story would benefit from some checklist items (think test plan).
Updated by elyezer about 8 years ago
bmbouter wrote:
Rather than position the name of the option about forcing or answering a yes/no quesiton, we could make the option disable the check altogether. Specifically I recommend naming it
--ignore-running-workers. This allows us to reserve a "force" language for something that actually need to be forced and also allows us to ask yes/no questions without having this new option be at all related to that.
Agreed, I like --ignore-running-workers option name.
Updated by bizhang about 8 years ago
- Assignee set to bizhang
Added by bizhang about 8 years ago
Added by bizhang about 8 years ago
Revision e0a950c5 | View on GitHub
Add --ignore-running-workers option to pulp-manage-db
Updated by bizhang about 8 years ago
- Status changed from NEW to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|e0a950c517bde193992d9f862e091cad56b1c223.
Added by bizhang about 8 years ago
Revision 18540126 | View on GitHub
Revert "Add --ignore-running-workers option to pulp-manage-db"
This reverts commit e0a950c517bde193992d9f862e091cad56b1c223.
Added by bizhang about 8 years ago
Revision 18540126 | View on GitHub
Revert "Add --ignore-running-workers option to pulp-manage-db"
This reverts commit e0a950c517bde193992d9f862e091cad56b1c223.
Updated by bizhang about 8 years ago
- Status changed from MODIFIED to NEW
- Assignee deleted (
bizhang) - % Done changed from 100 to 0
- Parent issue set to #2186
Updated by bmbouter over 5 years ago
- Status changed from NEW to CLOSED - WONTFIX
Updated by bmbouter over 5 years ago
Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the developer mailing list.
.
Add --ignore-running-workers option to pulp-manage-db
closes #2469 https://pulp.plan.io/issues/2469