Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1417079 - [Improvement] prevent running pulp-manage-db when pulp workers are up
Summary: [Improvement] prevent running pulp-manage-db when pulp workers are up
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.2.0
Hardware: All
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Bruno Rocha
URL:
Whiteboard:
Depends On: 1374723
Blocks: CEE_Sat6_Top_BZs, GSS_Sat6_Top_Bugs
TreeView+ depends on / blocked
 
Reported: 2017-01-27 07:55 UTC by Satellite Program
Modified: 2021-04-06 17:56 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of: 1374723
Environment:
Last Closed: 2018-02-21 16:33:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 2186 0 Normal CLOSED - CURRENTRELEASE As a user, pulp-manage-db refuses to run if other pulp processes are running 2017-02-01 21:01:59 UTC
Red Hat Knowledge Base (Solution) 2534911 0 None None None 2017-01-27 07:55:49 UTC
Red Hat Knowledge Base (Solution) 2607261 0 None None None 2017-01-27 07:55:49 UTC
Red Hat Knowledge Base (Solution) 2608761 0 None None None 2017-01-27 07:55:49 UTC

Comment 2 pulp-infra@redhat.com 2017-01-30 14:02:07 UTC 
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 3 pulp-infra@redhat.com 2017-01-30 14:02:13 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 4 pulp-infra@redhat.com 2017-02-01 21:02:00 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 5 Bruno Rocha 2017-12-18 18:08:39 UTC 
[root@cloud-qe-19 ~]# rpm -q satellite
satellite-6.3.0-23.0.el7sat.noarch

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


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:
	reserved_resource_worker-1@
	reserved_resource_worker-2@
	reserved_resource_worker-0@
	reserved_resource_worker-3@
	resource_manager@
	scheduler@

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.
 	reserved_resource_worker-1@
	reserved_resource_worker-2@
	reserved_resource_worker-0@
	reserved_resource_worker-3@
	resource_manager@
	scheduler@
Comment 6 Bryan Kearney 2018-02-21 16:33:29 UTC 
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/RHSA-2018:0336
Note You need to log in before you can comment on or make changes to this bug.