Bug 1898826
| Summary: | yum update failed to resolve dependencies | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Devendra Singh <desingh> |
| Component: | Packaging | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | Lukas Pramuk <lpramuk> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.9.0 | CC: | egolov, vsedmik |
| Target Milestone: | 6.9.0 | Keywords: | Regression, Triaged, Upgrades |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | satellite-6.9.0-0.3.beta | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-04-21 13:18:55 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: | |||
IMHO, foreman-proxy-content should not be installed on a Satelllite (only on a Capsule). In 6.9 we dropped the `satellite-capsule` RPM from the Satellite compose, and thus also foreman-proxy-content was removed. We *can* make the satellite RPM clean that up, but I'd argue this shouldn't be a blocker. Thanks, egolv, After removing the foreman-proxy-content package from the satellite the problem gets resolved. Same dependency issue spotted on Capsule server in `yum update` during upgrade:
---> Package tfm-rubygem-server_sent_events.noarch 0:0.1.2-1.el7sat will be installed
--> Finished Dependency Resolution
Error: Package: foreman-proxy-content-3.16.0-1.el7sat.noarch (@Sat6-CI_Satellite_Capsule_6_8_Composes_Satellite_Capsule_6_8_RHEL7)
Requires: katello-common = 3.16.0-1.el7sat
Removing: katello-common-3.16.0-1.el7sat.noarch (@Sat6-CI_Satellite_Capsule_6_8_Composes_Satellite_Capsule_6_8_RHEL7)
katello-common = 3.16.0-1.el7sat
Updated By: katello-common-3.18.0-0.1.rc1.el7sat.noarch (Sat6-CI_Satellite_6_9_Composes_Satellite_6_9_RHEL7)
katello-common = 3.18.0-0.1.rc1.el7sat
(In reply to Vladimír Sedmík from comment #3) > Same dependency issue spotted on Capsule server in `yum update` during > upgrade: > > ---> Package tfm-rubygem-server_sent_events.noarch 0:0.1.2-1.el7sat will be > installed > --> Finished Dependency Resolution > Error: Package: foreman-proxy-content-3.16.0-1.el7sat.noarch > (@Sat6-CI_Satellite_Capsule_6_8_Composes_Satellite_Capsule_6_8_RHEL7) > Requires: katello-common = 3.16.0-1.el7sat > Removing: katello-common-3.16.0-1.el7sat.noarch > (@Sat6-CI_Satellite_Capsule_6_8_Composes_Satellite_Capsule_6_8_RHEL7) > katello-common = 3.16.0-1.el7sat > Updated By: katello-common-3.18.0-0.1.rc1.el7sat.noarch > (Sat6-CI_Satellite_6_9_Composes_Satellite_6_9_RHEL7) > katello-common = 3.18.0-0.1.rc1.el7sat But the package *does* exist on Capsules still. Have a box I can SSH into? A note to whoever will read that in future: the machine, while being a Capsule, had the Satellite repos enabled, and then things went wrong. Confirmed with Vladimír on IRC that an upgrade with the correct repos passed this step fine. (In reply to Evgeni Golov from comment #4) > But the package *does* exist on Capsules still. > > Have a box I can SSH into? It seems there was satellite repo enabled before the first upgrade run, which caused the issue. I'm sorry for the confusion, please ignore the comment #3. VERIFIED.
@Satellite 6.9.0 Snap12
by the following manual reproducer:
REPRO:
# yum --disableplugin foreman-protector list foreman-proxy-content --showd
Loaded plugins: product-id, search-disabled-repos, subscription-manager
Available Packages
foreman-proxy-content.noarch 3.16.0-1.el7sat satellite
vs.
FIX:
# yum --disableplugin foreman-protector list foreman-proxy-content --showd
Loaded plugins: product-id, search-disabled-repos, subscription-manager
Error: No matching Packages to list
>>> there is no longer foreman-proxy-content package in satellite repo (while in capsule repo the package still exists)
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.9 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:1313 |
Description of problem: yum update failed to resolve dependencies. Version-Release number of selected component (if applicable): 6.9 How reproducible: always Steps to Reproduce: 1. Prepare the 6.8 setups for the upgrade. 2. Setup all the required repositories. 3. perform yum update -y 4. foreman-proxy-content-3.16.0-1.el7sat.noarch package fails to resolve dependencies ---> Package tfm-rubygem-server_sent_events.noarch 0:0.1.2-1.el7sat will be installed --> Finished Dependency Resolution Error: Package: foreman-proxy-content-3.16.0-1.el7sat.noarch (@rhel-7-server-satellite-6.8-rpms) Requires: katello-common = 3.16.0-1.el7sat Removing: katello-common-3.16.0-1.el7sat.noarch (@rhel-7-server-satellite-6.8-rpms) katello-common = 3.16.0-1.el7sat Updated By: katello-common-3.18.0-0.1.rc1.el7sat.noarch (sat6) katello-common = 3.18.0-0.1.rc1.el7sat ..... ..... ---> Package kernel.x86_64 0:3.10.0-1127.el7 will be erased --> Finished Dependency Resolution Error: Package: foreman-proxy-content-3.16.0-1.el7sat.noarch (@rhel-7-server-satellite-6.8-rpms) Requires: katello-common = 3.16.0-1.el7sat Removing: katello-common-3.16.0-1.el7sat.noarch (@rhel-7-server-satellite-6.8-rpms) katello-common = 3.16.0-1.el7sat Updated By: katello-common-3.18.0-0.1.rc1.el7sat.noarch (sat6) katello-common = 3.18.0-0.1.rc1.el7sat Actual results: foreman-proxy-content failed to resolve the dependencies. Expected results: All the packages should be updated successfully. Additional info: