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:
Yum-Cron emails contain an error related to broken or 'bad duplicate' update notice. Error is also displayed during yum check-update and does not clear after running 'yum clean all' and 'yum makecache' as previously suggested.
Version-Release number of selected component (if applicable):
yum-3.4.3-125.el7
How reproducible:
Every time starting around 6pm CDT.
Steps to Reproduce:
1. Run 'yum check-update' to receive error.
2. 'yum clean all && yum makecache && yum check-update' still gives error.
Actual results:
yum check-update gives list of available updates but is followed by:
Update notice RHSA-2014:0679 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the rhel-7-server-rpms repository.
Update notice RHSA-2014:1327 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHEA-2015:0372 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHBA-2015:0335 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHEA-2015:0371 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHSA-2015:0416 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHBA-2015:0303 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHBA-2015:0556 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHSA-2015:0290 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHBA-2015:0596 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHBA-2015:0578 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHSA-2015:0716 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Expected results:
Not seeing the above "Update notice [...] is broken, or a bad duplicate, skipping."
Additional info:
We have received a number of inquires about this today and I just wanted to ensure this is not either going to be an ongoing issue or is at least raised to the right place. Bugzilla does contain past references to very similar but not exact matching bugs (1203963, 960642, 1008067) and RedHat solutions also contains a workaround that did not resolve the issue (https://access.redhat.com/solutions/696833)
Thank you.
Comment 2Valentina Mukhamedzhanova
2015-04-27 11:15:23 UTC
*** This bug has been marked as a duplicate of bug 1203963 ***
I just installed a brand new RHEL 7.1 system and am having the same problem. Unfortunately, I am unable to see the bug this was marked as a duplicate of so I can't tell if there's a fix or workaround available...