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 shows:
Update notice RHBA-2017:2939 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Version-Release number of selected component (if applicable):
yum-3.4.3-154.el7.noarch
How reproducible:
always
Steps to Reproduce:
1. subscribe to rhel-7-server-rpms and rhel-7-server-optional-rpms
2. yum updateinfo -v
3. profit.
Actual results:
Update notice RHBA-2017:2939 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Expected results:
no warning message
Additional info:
removing yum's cache didn't help.
yum updateinfo -v
Loading "product-id" plugin
Loading "search-disabled-repos" plugin
Loading "subscription-manager" plugin
Updating Subscription Management repositories.
Config time: 4.136
Yum version: 3.4.3
rpmdb time: 0.000
Duplicate of RHBA-2017:2939 differs in some fields:
<<<<<<< rhel-7-server-rpms:updated
'2018-01-31 15:25:38 UTC'
=======
'2018-04-05 08:21:05 UTC'
>>>>>>> rhel-7-server-optional-rpms:updated
Update notice RHBA-2017:2939 (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.
If you are the owner, consider re-running the same command with --verbose to see the exact data that caused the conflict.
updateinfo time: 6.423
Building updates object
Setting up Package Sacks
pkgsack time: 0.034
up:Obs Init time: 0.877
up:simple updates time: 0.026
up:obs time: 0.007
up:condense time: 0.000
updates time: 2.196
updateinfo summary done
Is this situation still occurring? The repositories in question have been regenerated in their entirety several times since this bug was originally filed.
Still seeing this error:
[root@perf48 ~]# yum check-update --verbose
.
.
.
Duplicate of RHBA-2019:0862 differs in some fields:
<<<<<<< rhel-7-server-extras-rpms:version
'1'
=======
'2'
>>>>>>> rhel-7-server-extras-debug-rpms:version
Update notice RHBA-2019:0862 (from rhel-7-server-extras-rpms) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the rhel-7-server-extras-rpms repository.
If you are the owner, consider re-running the same command with --verbose to see the exact data that caused the conflict.
updateinfo time: 8.824
Reopening, it seems this is happening again, I have hourly reports from yum cron with the same info:
+++
/etc/cron.hourly/0yum-hourly.cron:
Update notice RHBA-2018:2796 (from rhel-7-server-extras-rpms) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the rhel-7-server-extras-rpms repository.
If you are the owner, consider re-running the same command with --verbose to see the exact data that caused the conflict.
---
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed.
From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."
If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook
Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product.
Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.
[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7
Happening again on all 28+ machines, every hour.
/etc/cron.hourly/0yum-hourly.cron:
Update notice RHSA-2020:1068 (from rhel-7-server-optional-debug-rpms) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the rhel-7-server-optional-debug-rpms repository.
If you are the owner, consider re-running the same command with --verbose to see the exact data that caused the conflict.
Update notice RHSA-2020:1068 (from rhel-7-server-optional-rpms) is broken, or a bad duplicate, skipping.
You should report this problem to the owner of the rhel-7-server-optional-rpms repository.
If you are the owner, consider re-running the same command with --verbose to see the exact data that caused the conflict.
Description of problem: yum shows: Update notice RHBA-2017:2939 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping. Version-Release number of selected component (if applicable): yum-3.4.3-154.el7.noarch How reproducible: always Steps to Reproduce: 1. subscribe to rhel-7-server-rpms and rhel-7-server-optional-rpms 2. yum updateinfo -v 3. profit. Actual results: Update notice RHBA-2017:2939 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping. Expected results: no warning message Additional info: removing yum's cache didn't help. yum updateinfo -v Loading "product-id" plugin Loading "search-disabled-repos" plugin Loading "subscription-manager" plugin Updating Subscription Management repositories. Config time: 4.136 Yum version: 3.4.3 rpmdb time: 0.000 Duplicate of RHBA-2017:2939 differs in some fields: <<<<<<< rhel-7-server-rpms:updated '2018-01-31 15:25:38 UTC' ======= '2018-04-05 08:21:05 UTC' >>>>>>> rhel-7-server-optional-rpms:updated Update notice RHBA-2017:2939 (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. If you are the owner, consider re-running the same command with --verbose to see the exact data that caused the conflict. updateinfo time: 6.423 Building updates object Setting up Package Sacks pkgsack time: 0.034 up:Obs Init time: 0.877 up:simple updates time: 0.026 up:obs time: 0.007 up:condense time: 0.000 updates time: 2.196 updateinfo summary done