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.
Bug 1898826 - yum update failed to resolve dependencies
Summary: yum update failed to resolve dependencies
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.9.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: 6.9.0
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-18 08:05 UTC by Devendra Singh
Modified: 2021-04-21 13:18 UTC (History)
2 users (show)

Fixed In Version: satellite-6.9.0-0.3.beta
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-21 13:18:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Devendra Singh 2020-11-18 08:05:25 UTC 
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:
Comment 1 Evgeni Golov 2020-11-18 11:20:33 UTC 
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.
Comment 2 Devendra Singh 2020-11-18 15:36:12 UTC 
Thanks, egolv, After removing the foreman-proxy-content package from the satellite the problem gets resolved.
Comment 3 Vladimír Sedmík 2020-11-24 11:07:21 UTC 
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
Comment 4 Evgeni Golov 2020-11-24 13:59:02 UTC 
(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?
Comment 5 Evgeni Golov 2020-11-24 18:05:59 UTC 
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.
Comment 6 Vladimír Sedmík 2020-11-24 18:09:47 UTC 
(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.
Comment 7 Lukas Pramuk 2021-02-12 00:47:59 UTC 
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)
Comment 10 errata-xmlrpc 2021-04-21 13:18:55 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.