Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Currently the pulp_celerybeat component periodically checks the list of known workers. That list includes the scheduler (pulp_celerybeat), the resource_manager, and some number of pulp_workers. Any of these three components can have multiple entries, but for correct Pulp operation, they all need to have at least one.
It would be useful and simple to have that check ensure that at least one of each type is present and log each type that is missing. I recommend logging at the 'error' level, and for each one, give a specific recommendation to the user about what process specifically is not running. Also indicate that Pulp will not function correctly without resolving this.
This has already been merged upstream so it's ready for cherry picking. See ref on the upstream bug.
Comment 1RHEL Program Management
2015-07-23 14:37:48 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 3pulp-infra@redhat.com
2015-07-23 15:00:21 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 4pulp-infra@redhat.com
2015-07-23 15:00:22 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 6pulp-infra@redhat.com
2015-10-22 15:01:05 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 7pulp-infra@redhat.com
2015-11-09 21:01:03 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
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-2016:1501