Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Product interoperability automation has caught a packaging problem during installation of satellite 6.11 on the RHEL8.8 compose (RHEL-8.8.0-20221220.0).
Satellite installer requires:
ansible-core >= 2.12 and ansible-core < 2.13
however rhel8.8 compose repository provides
ansible-core-2.14.0-1.el8.x86_64.rpm
https://download.eng.bos.redhat.com/rhel-8/nightly/RHEL-8/RHEL-8.8.0-20221220.0/
Version-Release number of selected component (if applicable):
6.11.4.1-1.el8sat
Actual results:
Depsolve Error occured: \n Problem: package satellite-6.11.4.1-1.el8sat.noarch requires satellite-common, but none of the providers can be installed\n - cannot install the best candidate for the job\n - nothing provides ((ansible >= 2.9 and ansible < 2.10) or (ansible-core >= 2.12 and ansible-core < 2.13)) needed by satellite-common-6.11.2-1.el8sat.noarch\n - nothing provides ((ansible >= 2.9 and ansible < 2.10) or (ansible-core >= 2.12 and ansible-core < 2.13)) needed by satellite-common-6.11.1-1.el8sat.noarch\n - nothing provides ((ansible >= 2.9 and ansible < 2.10) or (ansible-core >= 2.12 and ansible-core < 2.13)) needed by satellite-common-6.11.0-2.el8sat.noarch\n - nothing provides ((ansible >= 2.9 and ansible < 2.10) or (ansible-core >= 2.12 and ansible-core < 2.13)) needed by satellite-common-6.11.3-1.el8sat.noarch\n - nothing provides ((ansible >= 2.9 and ansible < 2.10) or (ansible-core >= 2.12 and ansible-core < 2.13)) needed by satellite-common-6.11.1.1-1.el8sat.noarch\n - nothing provides (ansible-core >= 2.12 and ansible-core < 2.14) needed by satellite-common-6.11.4-2.el8sat.noarch\n - nothing provides (ansible-core >= 2.12 and ansible-core < 2.14) needed by satellite-common-6.11.4.1-1.el8sat.noarch'
Expected results:
a matching, working ansible-core is installed
# rpm -qR satellite-common
(ansible-core >= 2.12 and ansible-core < 2.14)
^ problematic requires preventing to be installed along with ansible-core 2.14
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 (Important: Satellite 6.13 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-2023:2097