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.

Description of problem:

Pulp workers throw connection exceptions during a restart of katello services. This is due to the message broker being restarted before the workers are shut down. 

The services work properly afterwards, however, this looks bad to the user.



Steps to Reproduce:
  1. katello-service restart
  2. Look in logs
  3. See connection errors in log

Actual results:

  Errors in log

Expected results:

  No errors in log.

Hi Dennis,  can you attach a foreman-debug or other text that shows examples of the errors?

I don't have a sample of log output. Someone in #satellite6 mentioned seeing these errors in their logs. I looked at the order in which services are shut down and it made sense to me that it would possible for pulp workers to spew connection errors when the broker is shut down before the workers are turned off.

Moving 6.2 bugs out to sat-backlog.

This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.