Bug 1966435
| Summary: | Unable to configure cloud connector plugin because of package dependency issue. | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Jameer Pathan <jpathan> |
| Component: | RH Cloud - Cloud Connector | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Lukáš Hellebrandt <lhellebr> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.10.0 | CC: | aruzicka, ehelms, osousa, sshtein, vijsingh |
| Target Milestone: | 6.10.0 | Keywords: | PrioBumpQA, Regression, TestBlocker, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | receptor-0.6.4-2 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-16 14:11:21 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: | |||
Depends on receptor issue https://github.com/project-receptor/python-receptor/issues/230. Shim, are additional changes needed beyond the python-receptor update mentioned in comment 1? Thanks! Adding some context on why this affects Satellite this way. With Satellite 6.10, we introduce Pulp 3 which shares some packages with receptor (namely the ones erroring in the output). Pulp 3 requires new versions of those packages than receptor so when someone tries to enable Cloud Connector they hit this yum issue. As far as I know, those are the only packages that need changes. Fixes were merged in upstream and released. Hi Adam, the fixed version is 0.6.4 right? I can only see 0.6.3 released on Github. Correct. Looks like they didn't place a tag in the repo. There is 0.6.4 on pypi[1] though [1] - https://pypi.org/project/receptor/0.6.4/ Failed with Sat 6.10.0 snap 9.0:
Package installation fails both when installing through WebUI and when installing directly using yum:
Resolving Dependencies
--> Running transaction check
---> Package receptor.noarch 0:0.6.4-1.el7ar will be installed
--> Processing Dependency: python3-prometheus-client = 0.7.1 for package: receptor-0.6.4-1.el7ar.noarch
--> Processing Dependency: python3-aiohttp = 3.6.2 for package: receptor-0.6.4-1.el7ar.noarch
--> Processing Dependency: python3-dateutil >= 1:2.8.1 for package: receptor-0.6.4-1.el7ar.noarch
--> Finished Dependency Resolution
Error: Package: receptor-0.6.4-1.el7ar.noarch (Sat6-CI_Satellite_6_10_Composes_Satellite_6_10_RHEL7)
Requires: python3-dateutil >= 1:2.8.1
Installed: python3-dateutil-2.8.1-3.el7pc.noarch (@Sat6-CI_Satellite_6_10_Composes_Satellite_6_10_RHEL7)
python3-dateutil = 2.8.1-3.el7pc
Error: Package: receptor-0.6.4-1.el7ar.noarch (Sat6-CI_Satellite_6_10_Composes_Satellite_6_10_RHEL7)
Requires: python3-prometheus-client = 0.7.1
Installed: python3-prometheus-client-0.8.0-1.el7pc.noarch (@Sat6-CI_Satellite_6_10_Composes_Satellite_6_10_RHEL7)
python3-prometheus-client = 0.8.0-1.el7pc
Error: Package: receptor-0.6.4-1.el7ar.noarch (Sat6-CI_Satellite_6_10_Composes_Satellite_6_10_RHEL7)
Requires: python3-aiohttp = 3.6.2
Installed: python3-aiohttp-3.7.4-1.el7pc.x86_64 (@Sat6-CI_Satellite_6_10_Composes_Satellite_6_10_RHEL7)
python3-aiohttp = 3.7.4-1.el7pc
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
The Requirements where updated on receptor-0.6.4-2.el7ar, the fix should land in Snap 10. Verified with Sat 6.10.0 snap 10.0. Successfully installed receptor package both using yum and using the Configure Cloud Connector button in WebUI. Installing through the button, the receptor is correctly configured, running and FiFi end-to-end scenario works up to error "Playbook failed signature validation: /usr/bin/insights-client not found" happening on remediation application which is caused by a new feature. 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 (Moderate: Satellite 6.10 Release), 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-2021:4702 |
Description of problem: Unable to configure cloud connector plugin because of package dependency issue. Version-Release number of selected component (if applicable): - Satellite 6.10.0 snap 2 - python3-receptor-satellite.noarch 0:1.4.0-1.el7sat - ansiblerole-satellite-receptor-installer-0.6.13-1.el7sat.noarch How reproducible: - Always Steps to Reproduce: 1. Go to configure > Inventory upload 2. Click on "Configure Cloud connector" Actual results: - Cloud connector setup fails with package dependency error. Resolving Dependencies --> Running transaction check ---> Package python3-receptor-satellite.noarch 0:1.4.0-1.el7sat will be installed --> Processing Dependency: receptor for package: python3-receptor-satellite-1.4.0-1.el7sat.noarch --> Running transaction check ---> Package receptor.noarch 0:0.6.3-1.el7ar will be installed --> Processing Dependency: python3-prometheus-client = 0.7.1 for package: receptor-0.6.3-1.el7ar.noarch --> Processing Dependency: python3-aiohttp = 3.6.2 for package: receptor-0.6.3-1.el7ar.noarch --> Finished Dependency Resolution Error: Package: receptor-0.6.3-1.el7ar.noarch (Sat6-CI_Satellite_6_10_Composes_Satellite_6_10_RHEL7) Requires: python3-aiohttp = 3.6.2 Installed: python3-aiohttp-3.7.4-1.el7pc.x86_64 (@Sat6-CI_Satellite_6_10_Composes_Satellite_6_10_RHEL7) python3-aiohttp = 3.7.4-1.el7pc Error: Package: receptor-0.6.3-1.el7ar.noarch (Sat6-CI_Satellite_6_10_Composes_Satellite_6_10_RHEL7) Requires: python3-prometheus-client = 0.7.1 Installed: python3-prometheus-client-0.8.0-1.el7pc.noarch (@Sat6-CI_Satellite_6_10_Composes_Satellite_6_10_RHEL7) python3-prometheus-client = 0.8.0-1.el7pc You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Expected results: - No package dependency issue. Additional info: