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.

Bug 1056628

Summary: Appying security updates complains of broken or duplicate update notices
Product: Red Hat Enterprise Linux 6 Reporter: Sten Turpin <sten>
Component: yumAssignee: Packaging Maintenance Team <packaging-team-maint>
Status: CLOSED NOTABUG QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5CC: james.antill
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-25 15:59:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sten Turpin 2014-01-22 15:18:23 UTC 
Description of problem: Applied security updates with "yum -y --security update", got errors about broken or duplicate update notices


Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. Apply updates with "yum -y --security update"
2. Updates apply, but with stderr below


Actual results:
Stderr: An update notice is broken, or duplicate, skipping: RHSA-2013:1752
An update notice is broken, or duplicate, skipping: RHSA-2013:1764
An update notice is broken, or duplicate, skipping: RHSA-2013:1778
An update notice is broken, or duplicate, skipping: RHSA-2013:1829
An update notice is broken, or duplicate, skipping: RHSA-2013:1801
An update notice is broken, or duplicate, skipping: RHSA-2013:1803
An update notice is broken, or duplicate, skipping: RHSA-2013:1806
An update notice is broken, or duplicate, skipping: RHSA-2013:1813
An update notice is broken, or duplicate, skipping: RHSA-2013:1850
An update notice is broken, or duplicate, skipping: RHSA-2013:1752
An update notice is broken, or duplicate, skipping: RHSA-2013:1764
An update notice is broken, or duplicate, skipping: RHSA-2013:1778
An update notice is broken, or duplicate, skipping: RHSA-2013:1829
An update notice is broken, or duplicate, skipping: RHSA-2013:1801
An update notice is broken, or duplicate, skipping: RHSA-2013:1803
An update notice is broken, or duplicate, skipping: RHSA-2013:1806
An update notice is broken, or duplicate, skipping: RHSA-2013:1813
An update notice is broken, or duplicate, skipping: RHSA-2013:1850



Expected results:
Updates apply without error

Additional info:
yum history shows the transaction: 
Transaction ID : 316
Begin time     : Wed Jan 22 09:56:32 2014
Begin rpmdb    : 1674:e7c5beae7e9149b1f4e6cbc394e8b432c8d9730d
End time       :            09:57:20 2014 (48 seconds)
End rpmdb      : 1674:5722232f02ca4ca4eeb79f1d5af1e1b0405f1e9f
User           : root <root>
Return-Code    : Success
Command Line   : -y --security update
Transaction performed with:
    Installed     rpm-4.8.0-37.el6.x86_64                  @rhui-REGION-rhel-server-releases
    Installed     yum-3.2.29-40.el6.noarch                 @rhui-us-east-1-rhel-server-releases
    Installed     yum-plugin-security-1.1.30-14.el6.noarch @rhui-us-east-1-rhel-server-releases
Packages Altered:
    Updated augeas-libs-1.0.0-5.el6.x86_64                         @rhui-REGION-rhel-server-releases
    Update              1.0.0-5.el6_5.1.x86_64                     @rhui-REGION-rhel-server-releases
    Updated bind-libs-32:9.8.2-0.17.rc1.el6_4.6.x86_64             @rhui-REGION-rhel-server-releases
    Update            32:9.8.2-0.23.rc1.el6_5.1.x86_64             @rhui-REGION-rhel-server-releases
    Updated bind-utils-32:9.8.2-0.17.rc1.el6_4.6.x86_64            @rhui-REGION-rhel-server-releases
    Update             32:9.8.2-0.23.rc1.el6_5.1.x86_64            @rhui-REGION-rhel-server-releases
    Updated java-1.7.0-openjdk-1:1.7.0.45-2.4.3.4.el6_5.i686       @rhui-z-i386
    Update                     1:1.7.0.51-2.4.4.1.el6_5.i686       @rhui-z-i386
    Updated java-1.7.0-openjdk-devel-1:1.7.0.45-2.4.3.4.el6_5.i686 @rhui-z-i386
    Update                           1:1.7.0.51-2.4.4.1.el6_5.i686 @rhui-z-i386
Scriptlet output:
   1 warning: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.45/jre/lib/security/java.security saved as /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.45/jre/lib/security/java.security.rpmsave
Comment 2 Deepak Bhole 2014-01-22 15:49:57 UTC 
This seems to be an issue with yum rather than with OpenJDK. Re-assigning.
Comment 3 James Antill 2014-03-25 15:59:06 UTC 
 This is just printing out warnings about problems in the remote repodata. It's mostly harmless, but the repodata should get fixed (if only to remove these messages).