Red Hat Bugzilla – Bug 1374723
[Improvement] prevent running pulp-manage-db when pulp workers are up
Last modified: 2018-09-19 11:12:46 EDT
Description of problem: If pulp-manage-db is executed (due to whatever user/doc error) when pulp workers are running, various collections in mongo can violate their unique indices. Removing the duplicates is quite challenging, esp. because there is no relation model of pulp_database so one does not simply know where all could references to the duplicates be hidden. This situation is not rare, it happened to 3 customers at least. Please add to pulp-manage-db a test checking if some worker is running, and if so, stop the tool (or require human confirmation to continue). See https://pulp.plan.io/issues/2186 raised in upstream. Version-Release number of selected component (if applicable): pulp-server-2.8.3.4-1.el7sat.noarch How reproducible: 100% Steps to Reproduce: 1. for i in pulp_resource_manager pulp_workers pulp_celerybeat; do service $i start; done 2. pulp-manage-db Actual results: 2. is executed without a warning or so Expected results: 2. should be stopped with an error that pulp workers are running, or the tool should require user confirmation to proceed. Additional info:
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
*** Bug 1371677 has been marked as a duplicate of this bug. ***
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Verified in: satellite-6.2.8-1.0.el7sat.noarch Results: [root@fqdn.com ~]# for i in pulp_resource_manager pulp_workers pulp_celerybeat; do service $i start; done Redirecting to /bin/systemctl start pulp_resource_manager.service Redirecting to /bin/systemctl start pulp_workers.service Redirecting to /bin/systemctl start pulp_celerybeat.service [root@fqdn.com ~]# sudo -u apache pulp-manage-db Attempting to connect to localhost:27017 Attempting to connect to localhost:27017 Write concern for Mongo connection: {} The following processes might still be running: scheduler@fqdn.com resource_manager@fqdn.com reserved_resource_worker-0@fqdn.com reserved_resource_worker-1@fqdn.com reserved_resource_worker-3@fqdn.com reserved_resource_worker-2@fqdn.com Please wait 1 seconds while Pulp confirms this. The following processes are still running, please stop the running workers before retrying the pulp-manage-db command. scheduler@fqdn.com resource_manager@fqdn.com reserved_resource_worker-0@fqdn.com reserved_resource_worker-1@fqdn.com reserved_resource_worker-3@fqdn.com reserved_resource_worker-2@fqdn.com
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:0447