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.

Description of problem:
When upgrading (in my case from 6.9.3 s2.0 to 6.10.0 7.0), the upgrade fails because it can't start services pulp_celerybeat and pulp_resource_manager. Journalctl shows the services are missing a qpidtoollibs python package:

```
File "/usr/lib/python2.7/site-packages/kombu/transport/qpid.py", line 1472, in verify_runtime_environment()
'The Python package "qpidtoollibs" is missing. Install it '
RuntimeError: The Python package "qpidtoollibs" is missing. Install it with your package manager. You can also try `pip install qpid-tools`.
```

Full traceback attached.

Version-Release number of selected component (if applicable):
6.10.0 s7.0

How reproducible:
Deterministic

Steps to Reproduce:
1. Upgrade a Satellite to 6.10.0 s7.0

Actual results:
Upgrade failed, services won't start

Expected results:
Successfull upgrade and a working Sat 6.10.0 s7.0

Created attachment 1797121 [details]
journalctl_celerybeat.txt

Celerybeat traceback. It's similar for resource manager.

With recent snaps, is this issue still happening?

Given that upgrade testing is not finding this issue, I am going to opt to close this as not a bug. If this happens again, please re-open.