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 2051374 - wrong sinatra obsoletes makes Satellite uninstallable
Summary: wrong sinatra obsoletes makes Satellite uninstallable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Packaging
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.11.0
Assignee: satellite6-bugs
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-07 06:56 UTC by Evgeni Golov
Modified: 2022-07-05 14:33 UTC (History)
2 users (show)

Fixed In Version: satellite-7.0.0-0.5.beta,satellite-7.0.0-0.6.beta
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-05 14:32:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:5498 0 None None None 2022-07-05 14:33:04 UTC

Description Evgeni Golov 2022-02-07 06:56:10 UTC 
Description of problem:
Error: 
 Problem 1: package rubygem-foreman-tasks-5.2.1-1.el8sat.noarch requires rubygem(sinatra), but none of the providers can be installed
  - package satellite-common-7.0.0-0.4.beta.el8sat.noarch obsoletes rubygem-sinatra provided by rubygem-sinatra-2.1.0-2.el8sat.noarch
  - cannot install the best update candidate for package rubygem-sinatra-2.1.0-2.el8sat.noarch
  - cannot install the best update candidate for package rubygem-foreman-tasks-5.2.0-1.el8sat.noarch
 Problem 2: package foreman-proxy-3.1.1-1.el8sat.noarch requires rubygem(sinatra), but none of the providers can be installed
  - package satellite-common-7.0.0-0.4.beta.el8sat.noarch obsoletes rubygem-sinatra provided by rubygem-sinatra-2.1.0-2.el8sat.noarch
  - cannot install the best update candidate for package satellite-common-7.0.0-0.3.beta.el8sat.noarch
  - cannot install the best update candidate for package foreman-proxy-3.1.1-1.el8sat.noarch
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)


Version-Release number of selected component (if applicable):
Satellite 7.0 Snap 8 on EL8

How reproducible:
100%

Steps to Reproduce:
1. dnf install satellite


Actual results:
see above

Expected results:
it works ;)

Additional info:
rubygem-sinatra on EL7, that we used to ship ended with 1:1.4.7-3, so we need to obsolete < 1:1.4.7-4, BUT due to this pkg having an epoch, and the version on EL8 NOT having an epoch, we can't use the same obsolete on EL8 too!
Comment 2 Lukas Pramuk 2022-02-08 13:53:47 UTC 
Based on Evgeni's comment I think we still should have rubygem-sinatra = 1:2.1.0-2.el8sat (keeping the epoch 1:) as it's not a really good practice to lose epoch from newer rpm builds
Comment 3 Lukas Pramuk 2022-02-09 13:53:23 UTC 
Filed BZ #2052524 - rubygem-sinatra el8 rpm should keep the epoch number
Comment 4 Lukas Pramuk 2022-02-17 22:00:24 UTC 
VERIFIED.

@Satellite 7.0.0 Snap9
satellite-common-7.0.0-0.5.beta.el8sat.noarch

by reproducer described in comment#0:

1) Enable CDN repos and set up SAT 7.0 compose repos

2) Enabled modules streams integration

# yum -y module enable ruby:2.7 pki-core python38 redis
# yum-config-manager --setopt=*.module_hotfixes=1 --save satellite*

3) Install satellite rpm or RHEL8

# yum -y install satellite
Updating Subscription Management repositories.
Last metadata expiration check: 0:01:27 ago on Thu 17 Feb 2022 08:12:07 AM EST.
Dependencies resolved.
========================================================================================================================
 Package                        Arch   Version                                   Repository                        Size
========================================================================================================================
Installing:
 satellite                      noarch 7.0.0-0.5.beta.el8sat                     satellite                         17 k
Installing dependencies:
...

Complete!

>>> satellite rpm installed successfully on RHEL8

# rpm -q --obsoletes satellite-common
<empty>

>>> there are no obsoletes required for rhel8
Comment 9 errata-xmlrpc 2022-07-05 14:32:45 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.11 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-2022:5498
Note You need to log in before you can comment on or make changes to this bug.