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:
Version-Release number of selected component (if applicable):
How reproducible: Always
Steps to Reproduce:
1. yum check-update --verbose
Actual results:
Duplicate of RHBA-2018:0042 differs in some fields:
<<<<<<< rhui-REGION-rhel-server-releases:updated
'2018-01-04 22:22:50 UTC'
=======
'2019-08-13 07:21:22 UTC'
>>>>>>> rhui-REGION-rhel-server-optional:updated
Update notice RHBA-2018:0042 (from rhui-REGION-rhel-server-releases) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the rhui-REGION-rhel-server-releases repository.
If you are the owner, consider re-running the same command with --verbose to see the exact data that caused the conflict.
Duplicate of RHBA-2019:2358 differs in some fields:
<<<<<<< rhui-REGION-rhel-server-releases:version
'1'
=======
'2'
>>>>>>> rhui-REGION-rhel-server-optional:version
Update notice RHBA-2019:2358 (from rhui-REGION-rhel-server-releases) is broken, or a bad duplicate, skipping.
updateinfo time: 3.935
Expected results:
No error message
Additional info:
[root@acpt-rhel-anm-b yum.repos.d]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.7 (Maipo)
[root@acpt-rhel-anm-b yum.repos.d]# uname -a
Linux redactedhostname 3.10.0-1062.el7.x86_64 #1 SMP Thu Jul 18 20:25:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
REGION is us-east-1
[rhui-REGION-rhel-server-releases]
name=Red Hat Enterprise Linux Server 7 (RPMs)
mirrorlist=https://rhui2-cds01.REGION.aws.ce.redhat.com/pulp/mirror/content/dist/rhel/rhui/server/7/$releasever/$basearch/os
[rhui-REGION-rhel-server-debug-optional]
name=Red Hat Enterprise Linux Server 7 Optional Debug (Debug RPMs)
mirrorlist=https://rhui2-cds01.REGION.aws.ce.redhat.com/pulp/mirror/content/dist/rhel/rhui/server/7/$releasever/$basearch/optional/debug
I see I somehow missed
Description of problem:
When doing a yum update or yum-checkupdate on my RHEL AWS ec2 instances, I get an error message about some duplication of repositories, and an apparent mis-match between the two.
These messages are a known issue; they sometimes happen with advisories which span multiple repos and their metadata go out of sync. It's already extensively tracked here:
https://bugzilla.redhat.com/show_bug.cgi?id=1203963
The recommended workaround is to try cleaning the yum cache ("yum clean metadata") and trying again later. Sometimes, it takes a few days for the affected repos to get in sync again, at which point yum no longer complains about these advisories and loads them properly.
That being said, I'm closing this as a dupe of the above bug, as the general issue should be resolved on the CDN side.
*** This bug has been marked as a duplicate of bug 1203963 ***