For pulp-manage-db prerequisites: Add pulp_streamer to list of services that should not be running
https://github.com/pulp/pulp/pull/2903/files has docs/user-guide/release-notes/2.12.x.rst changes which list the other services but omit pulp_streamer.service:
"``pulp-manage-db`` will not continue if pulp_celerybeat, pulp_resource_manager, or pulp_workers
+ processes are running. This will prevent the user from corrupting their Pulp installation by
+ migrating with running workers. This works in both standalone and clustered installations. Pulp
+ may wait up to 92 seconds to determine if workers are running."
#1 Updated by bmbouter about 3 years ago
First off, I'm delighted you filed this. It's not often a non-core member points out a pre-beta issue in the code!
In this case (unfortunately) the note is correct. Currently, Pulp is not able to check if
httpd are running. I can understand wanting to have those check also, but that would be a new feature since we would need those components to "heartbeat" like
pulp_workers do today.
So given ^ do you want to file two new stories requesting that functionality? One for
pulp_streamer and one for
httpd? Since the docs are correct, I think this should be closed as NOTABUG.
@tcarlin, what do you think?
#2 Updated by firstname.lastname@example.org about 3 years ago
- There should be some type of warning to administrators since the result may be Pulp database corruption. This was my original intent in filing this issue
- I agree with you that determining if pulp_streamer or httpd would indeed be separate issues. I will file them so the work is properly segregated.
Thank you for your thoughtful response.
#3 Updated by bmbouter about 3 years ago
In order to do that, we need those components to heartbeat so I've created tasks for each of those as #2534 and #2535. Those would have to be done first, so I added a blocking relationship between the issues.
@tcarlin, how does ^ sound?
Please register to edit this issue