Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
We have a Satellite Proxy Server that we use and I just logged into update the server to RHEL 6.5 with a standard yum update. One of the packages that was to be updated was rhnlib. The current version is rhnlib-2.5.22-12.el6.noarch and there appears to be an update to 2.5.22-15.el6. However, a dependency of having a newer version of rhncfg is causing a conflict. See below in the actual results for the exact conversation.
Version-Release number of selected component (if applicable):
rhnlib-2.5.22-12.el6.noarch
How reproducible:
Always.
Steps to Reproduce:
1. Simply running a yum update rhnlib.
2.
3.
Actual results:
[root@rhnproxy1 ~]# yum -y update rhnlib
Loaded plugins: product-id, rhnplugin, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
This system is receiving updates from RHN Classic or RHN Satellite.
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package rhnlib.noarch 0:2.5.22-12.el6 will be updated
---> Package rhnlib.noarch 0:2.5.22-15.el6 will be an update
--> Processing Conflict: rhnlib-2.5.22-15.el6.noarch conflicts rhncfg < 5.10.27-13
--> Finished Dependency Resolution
Error: rhnlib conflicts with rhncfg-5.9.27-20.el6sat.noarch
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Expected results:
Clean update.
Additional info:
This is not a but. Apparently rhncfg was moved to a different RHN channel. Once I added that channel everything worked as expected. Please close this one out as it is not a bug.
Yes, new rhnlib and rhncfg packages were released to coincide with each other.
rhnlib is released in the main RHEL channels.
rhncfg-* packages are released in the RHN Tools child channel.
Closing out.