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.
Created attachment 1547653[details]
output from yum check-updates --verbose
Description of problem:
yum check-updates reports 400+ of ...
Update notice RHBA-xxxx:yyyy (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
see attached for --verbose output. This shows that there is a "\n" difference between notices in rhel-7-server-rpms and rhel-7-optional-rpms
Version-Release number of selected component (if applicable):
# yum --version
3.4.3
Installed: rpm-4.11.3-35.el7.x86_64 at 2018-10-30 04:37
Built : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2018-06-19 12:48
Committed: Pavlina Moravcova Varekova <pmoravco> at 2018-06-19
Installed: subscription-manager-1.21.10-3.el7_6.x86_64 at 2018-11-13 03:17
Built : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2018-11-07 19:14
Committed: Christopher Snyder <csnyder> at 2018-11-07
Installed: yum-3.4.3-161.el7.noarch at 2018-10-30 04:37
Built : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> at 2018-08-15 16:10
Committed: Michal Domonkos <mdomonko> at 2018-08-15
How reproducible:
Always, with both rhel-7-server-rpms and rhel-7-optional-rpms enabled. Obviously, yum check-updates runs normally if either repo is disabled.
Steps to Reproduce:
1. enable repos rhel-7-server-rpms and rhel-7-optional-rpms
2. run yum check-updates
Actual results:
See attached.
Expected results:
No notices. Either the summary information needs to be the same, or yum needs to become tolerant of minor differences, such as the trailing "\n" change here.
Additional info:
Problem was being reported hourly from /etc/cron.hourly/0yum-hourly.cron (yum-cron rpm).
First was at 2019-03-25 01:11. Last at 2019-03-26 00:08. None since. Presumably the repo info has been updated to resolve the problem.
However, there may still be a case for improving yum to ignore minor differences like the trailing new line that caused the problem here?
This issue comes up from time to time, unfortunately, and is caused by small inconsistencies in the updateinfo data from CDN. We are actively resolving them as they come up so it's likely that these particular issues are gone by now. If not, please keep an eye on the following bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1203963
*** This bug has been marked as a duplicate of bug 1203963 ***