Bug 1978623

Summary: qpidtoollibs missing after upgrade
Product: Red Hat Satellite Reporter: Lukáš Hellebrandt <lhellebr>
Component: UpgradesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED NOTABUG QA Contact: Devendra Singh <desingh>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.10.0CC: ehelms
Target Milestone: 6.10.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-12 14:48:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journalctl_celerybeat.txt none

Description Lukáš Hellebrandt 2021-07-02 10:33:16 UTC 
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
Comment 2 Lukáš Hellebrandt 2021-07-02 10:39:08 UTC 
Created attachment 1797121 [details]
journalctl_celerybeat.txt

Celerybeat traceback. It's similar for resource manager.
Comment 3 Eric Helms 2021-07-27 15:55:40 UTC 
With recent snaps, is this issue still happening?
Comment 6 Eric Helms 2021-08-12 14:48:36 UTC 
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.