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.
Bug 1194915 - Duplicate entries in updateinfo.xml reports unnecessary errors
Summary: Duplicate entries in updateinfo.xml reports unnecessary errors
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: yum
Version: 7.0
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Michal Domonkos
QA Contact: Eva Mrakova
URL:
Whiteboard:
: 1467764 (view as bug list)
Depends On:
Blocks: 1380360 1393866
TreeView+ depends on / blocked
 
Reported: 2015-02-20 22:29 UTC by Pat Riehecky
Modified: 2017-08-01 09:07 UTC (History)
13 users (show)

Fixed In Version: yum-3.4.3-151.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 09:07:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
rpm -q yum; yum clean all; yum makecache # On perf34, RHEL 7.4 Beta (16.88 KB, text/plain)
2017-05-27 02:37 UTC, Peter Portante 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1203963 0 urgent CLOSED Yum check-update reports broken update notices 2024-03-25 14:54:31 UTC
Red Hat Product Errata RHBA-2017:2295 0 normal SHIPPED_LIVE yum bug fix and enhancement update 2017-08-01 12:40:03 UTC

Description Pat Riehecky 2015-02-20 22:29:28 UTC 
Description of problem:
When yum-security finds an entry ID in an updateinfo.xml which it has already found it reports an error.  This makes sense when the xml stanzas differ, but when the stanzas are identical this results in an error message.

For example, my private repo includes some packages from EPEL in order to ensure the repo is appropriately closed.  I have copied in the relevant stanzas out of the EPEL updateinfo and added my own for my packages.  When I enable EPEL on this system for other packages I receive a string of error messages about duplicate update IDs.

Since the content of the updateinfo stanza is identical, I would not expect this to report an error.  Yum does not report an error on the identical rpm package.

Version-Release number of selected component (if applicable):yum-3.4.3-118.el7


How reproducible:100%


Steps to Reproduce:
1.install EPEL repo
2.create a local repo with the EPEL version of mock and its updateinfo stanza
3.you should now have two repos with different names that both contain the exact same version of mock and its updateinfo stanza
4. yum install mock
5. yum downgrade mock
6. yum check-update

Actual results:
Update notice FEDORA-EPEL-2014-2760 (from epel) is broken, or a
bad duplicate, skipping.
You should report this problem to the owner of the epel repository.

Expected results:
No errors about duplicate xml stanza since the stanzas are identical.

Additional info:
update_md.py around line 634
Comment 3 Stefanie Forrester 2015-10-12 19:58:00 UTC 
Here is some additional information on the issue. We're seeing this on systems that have only RHEL7 and RHEL7-optional repos enabled.

[root@64RHEL7 ~]# yum --disablerepo=* --enablerepo=rhel-7-server-rpms updateinfo
Loaded plugins: product-id, subscription-manager
updateinfo summary done

[root@64RHEL7 ~]# yum --disablerepo=* --enablerepo=rhel-7-server-rpms --enablerepo=rhel-7-server-optional-rpms updateinfo
Loaded plugins: product-id, subscription-manager
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.
Update notice RHSA-2015:1115 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHBA-2015:1533 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHSA-2015:1586 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
Update notice RHSA-2015:1705 (from rhel-7-server-rpms) is broken, or a bad duplicate, skipping.
updateinfo summary done
Comment 4 Akemi Yagi 2015-10-12 20:47:48 UTC 
I confirm Stefanie's comment. I've got the identical output on my RHEL-7 system.
Comment 5 Valentina Mukhamedzhanova 2015-10-13 09:12:06 UTC 
The issue described in comment 3 is unlikely the same as reported in this bugzilla, but rather the same as the issue reported in bug#1269265.
Comment 10 Michal Domonkos 2017-01-03 17:28:14 UTC 
(In reply to Pat Riehecky from comment #0)
> Description of problem:
> When yum-security finds an entry ID in an updateinfo.xml which it has
> already found it reports an error.  This makes sense when the xml stanzas
> differ, but when the stanzas are identical this results in an error message.
> 
> For example, my private repo includes some packages from EPEL in order to
> ensure the repo is appropriately closed.  I have copied in the relevant
> stanzas out of the EPEL updateinfo and added my own for my packages.  When I
> enable EPEL on this system for other packages I receive a string of error
> messages about duplicate update IDs.
> 
> Since the content of the updateinfo stanza is identical, I would not expect
> this to report an error.  Yum does not report an error on the identical rpm
> package.

For identical stanzas (assuming you mean the <update/> element and its content), yum really shouldn't throw the bad duplicate error (and it really didn't for me when I reproduced the same scenario).  Is it possible that you modified some part of the <update/> element's content in the copy you used in your repo?  Yum requires the duplicates to be exactly the same (except for <pkglist/> which is allowed to differ), including any whitespace chars, otherwise the error is thrown.

There have been similar issues with RH*A advisories distributed via RHN/CDN, where two logically same update notices would be reported as being bad duplicates because of them being inconsistent in some unicode/whitespace chars (also reported in comments #3 and #4 and bug 1269659).

Upstream yum contains a patch [1] that makes it easier to debug these issues by printing in --verbose mode the exact fields that don't match, so let's use this BZ to backport it into RHEL-7.  That may also help you to find the cause of the issue you had (if it's still current).

[1] https://github.com/rpm-software-management/yum/commit/533a3e3b23ba5263e7c17fd9a4e165c4e25d158e
Comment 15 Karel Srot 2017-05-25 20:59:55 UTC 
Hi Michal,
see bug 1203963, there still seem to be some issues reported.
Comment 18 Peter Portante 2017-05-27 02:37:45 UTC 
Created attachment 1282800 [details]
rpm -q yum; yum clean all; yum makecache  # On perf34, RHEL 7.4 Beta
Comment 19 Karel Srot 2017-07-11 09:13:52 UTC 
*** Bug 1467764 has been marked as a duplicate of this bug. ***
Comment 20 errata-xmlrpc 2017-08-01 09:07:52 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2295
Note You need to log in before you can comment on or make changes to this bug.