This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 2196763 - Installing latest rh-sso7-keycloak-server and eap7-wildfly-modules packages break any new transaction due to "obsoletes" information
Summary: Installing latest rh-sso7-keycloak-server and eap7-wildfly-modules packages b...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libsolv
Version: 8.7
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Jaroslav Mracek
QA Contact: swm-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-10 07:23 UTC by Renaud Métrich
Modified: 2023-09-01 22:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-01 22:36:38 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-1448 0 None Migrated None 2023-09-01 22:36:32 UTC
Red Hat Issue Tracker RHELPLAN-156885 0 None None None 2023-05-10 12:38:19 UTC

Description Renaud Métrich 2023-05-10 07:23:10 UTC
Description of problem:

Package "rh-sso7-keycloak-server-18.0.6-1.redhat_00001.1.el8sso.noarch" obsoletes some ancient "eap7-wildfly-modules" releases:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# rpm -q --obsoletes rh-sso7-keycloak-server-18.0.6-1.redhat_00001.1.el8sso.noarch
eap7-wildfly-modules <= 0:7.3
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Trying to install both rh-sso7-keycloak-server-18.0.6-1.redhat_00001.1.el8sso.noarch and eap7-wildfly-modules-7.4.10-6.GA_redhat_00002.1.el8eap (*latest, not obsoleted at all*) on the system, the eap7-wildfly-modules-7.4.10-6.GA_redhat_00002.1.el8eap cannot be installed, unless full release is explicitly specified:

1. The following doesn't install "eap7-wildfly-modules" at all

  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
  # yum install rh-sso7-keycloak-server eap7-wildfly-modules
  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

2. The following installs "eap7-wildfly-modules"

  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
  # yum install rh-sso7-keycloak-server eap7-wildfly-modules-7.4.10-6.GA_redhat_00002.1.el8eap
  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

I understand this is somehow expected because libsolv doesn't check the obsoleted part ("0:7.3") by default. Please correct me if I'm wrong.

Still this is an issue, because after installing the packages (using "2." method), any new "yum update" transaction will fail:

-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# yum update
[...]
Error: 
 Problem: cannot install both rh-sso7-keycloak-server-18.0.0-2.redhat_00001.1.el8sso.noarch and rh-sso7-keycloak-server-18.0.6-1.redhat_00001.1.el8sso.noarch
  - cannot install the best update candidate for package rh-sso7-keycloak-server-18.0.6-1.redhat_00001.1.el8sso.noarch
  - cannot install the best update candidate for package eap7-wildfly-modules-7.4.10-6.GA_redhat_00002.1.el8eap.noarch
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Version-Release number of selected component (if applicable):

libsolv-0.7.20-4.el8_7.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Install both packages, "eap7-wildfly-modules" being fully specified

  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
  # yum install rh-sso7-keycloak-server eap7-wildfly-modules-7.4.10-6.GA_redhat_00002.1.el8eap
  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

2. Try updating the system

  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
  # yum update
  -------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Actual results:

-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Error: 
 Problem: cannot install both rh-sso7-keycloak-server-18.0.0-2.redhat_00001.1.el8sso.noarch and rh-sso7-keycloak-server-18.0.6-1.redhat_00001.1.el8sso.noarch
  - cannot install the best update candidate for package rh-sso7-keycloak-server-18.0.6-1.redhat_00001.1.el8sso.noarch
  - cannot install the best update candidate for package eap7-wildfly-modules-7.4.10-6.GA_redhat_00002.1.el8eap.noarch
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Expected results:

No error

Comment 1 Renaud Métrich 2023-05-10 07:27:49 UTC
From the error, it seems that libsolv wants to downgrade rh-sso7-keycloak-server-18.0.6-1.redhat_00001.1.el8sso.noarch to rh-sso7-keycloak-server-18.0.0-2.redhat_00001.1.el8sso.noarch.

Note that rh-sso7-keycloak-server-18.0.0-2.redhat_00001.1.el8sso.noarch (old package) has a "wider obsolete" since it's obsoletes "eap7-wildfly-modules" completely:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# rpm -q --obsoletes -p ./rh-sso7-keycloak-server-18.0.0-2.redhat_00001.1.el8sso.noarch.rpm
eap7-wildfly-modules
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

It looks like this is exact root cause, at least excluding the package works:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# yum update --exclude=rh-sso7-keycloak-server-18.0.0-2.redhat_00001.1.el8sso
[...]
Nothing to do.
Complete!
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

If that's the real root cause, then this package has to be entirely removed from our repository since it can be considered as broken.

Comment 2 Jaroslav Mracek 2023-07-20 09:25:20 UTC
May I ask you from which repository is the package. I am unable to find it. If the issue is caused by incorrect packaging I would suggest to change the component for the package or to distribution.

Comment 3 Renaud Métrich 2023-08-07 05:55:29 UTC
As found in Package Browser, package rh-sso7-keycloak-server-18.0.0-2.redhat_00001.1.el8sso.noarch comes from rh-sso-7.6-for-rhel-8-x86_64-rpms

Comment 5 RHEL Program Management 2023-08-18 07:27:38 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 6 RHEL Program Management 2023-09-01 22:36:38 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues.

Users watching this BZ may not be automatically added to the Jira ticket.  Be sure to add yourself to the Watchers field in the Jira issue if you desire to continue following this issue.


Note You need to log in before you can comment on or make changes to this bug.