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 1390311 - Fix packaging duplicates of classes in multiple jar files
Summary: Fix packaging duplicates of classes in multiple jar files
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core
Version: 7.3
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: RHCS Maintainers
QA Contact: Asha Akkiangady
URL:
Whiteboard:
Depends On: 1386424
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-31 16:29 UTC by Tom Lavigne
Modified: 2016-12-06 17:04 UTC (History)
13 users (show)

Fixed In Version: pki-core-10.3.3-12.el7_3
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1386424
Environment:
Last Closed: 2016-12-06 17:04:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2881 0 normal SHIPPED_LIVE pki-core bug fix update 2016-12-06 22:00:37 UTC

Description Tom Lavigne 2016-10-31 16:29:28 UTC 
This bug has been copied from bug #1386424 and has been proposed
to be backported to 7.3 z-stream (EUS).
Comment 4 Roshni 2016-11-02 20:39:08 UTC 
Matt,

I am trying to verify this bug by executing the instructions in https://bugzilla.redhat.com/show_bug.cgi?id=1386424#c2

I see the following for tks and tps 

[root@auto-hv-01-guest01 pki]# grep -F -x -f pki-cms.jar.manifest pki-tks.jar.manifest 
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  01-01-1980 00:00   META-INF/
        0  01-01-1980 00:00   com/
        0  01-01-1980 00:00   com/netscape/
        0  01-01-1980 00:00   org/
        0  01-01-1980 00:00   org/dogtagpki/
        0  01-01-1980 00:00   org/dogtagpki/server/
---------                     -------
[root@auto-hv-01-guest01 pki]# grep -F -x -f pki-cms.jar.manifest pki-tps.jar.manifest 
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  01-01-1980 00:00   META-INF/
        0  01-01-1980 00:00   org/
        0  01-01-1980 00:00   org/dogtagpki/
        0  01-01-1980 00:00   org/dogtagpki/server/
---------                     -------


which is different from results you have provided. Please confirm if this bug can be marked Verified with the above results.
Comment 5 Matthew Harmsen 2016-11-04 18:15:38 UTC 
(In reply to Roshni from comment #4)
> Matt,
> 
> I am trying to verify this bug by executing the instructions in
> https://bugzilla.redhat.com/show_bug.cgi?id=1386424#c2
> 
> I see the following for tks and tps 
> 
> [root@auto-hv-01-guest01 pki]# grep -F -x -f pki-cms.jar.manifest
> pki-tks.jar.manifest 
>   Length      Date    Time    Name
> ---------  ---------- -----   ----
>         0  01-01-1980 00:00   META-INF/
>         0  01-01-1980 00:00   com/
>         0  01-01-1980 00:00   com/netscape/
>         0  01-01-1980 00:00   org/
>         0  01-01-1980 00:00   org/dogtagpki/
>         0  01-01-1980 00:00   org/dogtagpki/server/
> ---------                     -------
> [root@auto-hv-01-guest01 pki]# grep -F -x -f pki-cms.jar.manifest
> pki-tps.jar.manifest 
>   Length      Date    Time    Name
> ---------  ---------- -----   ----
>         0  01-01-1980 00:00   META-INF/
>         0  01-01-1980 00:00   org/
>         0  01-01-1980 00:00   org/dogtagpki/
>         0  01-01-1980 00:00   org/dogtagpki/server/
> ---------                     -------
> 
> 
> which is different from results you have provided. Please confirm if this
> bug can be marked Verified with the above results.

The important thing is the missing "com/" and "com/netscape/" in pki-tps.jar.manifest, so yes -- you may mark this bug VERIFIED.
Comment 6 Matthew Harmsen 2016-11-04 18:21:12 UTC 
(In reply to Matthew Harmsen from comment #5)
> (In reply to Roshni from comment #4)
> > Matt,
> > 
> > I am trying to verify this bug by executing the instructions in
> > https://bugzilla.redhat.com/show_bug.cgi?id=1386424#c2
> > 
> > I see the following for tks and tps 
> > 
> > [root@auto-hv-01-guest01 pki]# grep -F -x -f pki-cms.jar.manifest
> > pki-tks.jar.manifest 
> >   Length      Date    Time    Name
> > ---------  ---------- -----   ----
> >         0  01-01-1980 00:00   META-INF/
> >         0  01-01-1980 00:00   com/
> >         0  01-01-1980 00:00   com/netscape/
> >         0  01-01-1980 00:00   org/
> >         0  01-01-1980 00:00   org/dogtagpki/
> >         0  01-01-1980 00:00   org/dogtagpki/server/
> > ---------                     -------
> > [root@auto-hv-01-guest01 pki]# grep -F -x -f pki-cms.jar.manifest
> > pki-tps.jar.manifest 
> >   Length      Date    Time    Name
> > ---------  ---------- -----   ----
> >         0  01-01-1980 00:00   META-INF/
> >         0  01-01-1980 00:00   org/
> >         0  01-01-1980 00:00   org/dogtagpki/
> >         0  01-01-1980 00:00   org/dogtagpki/server/
> > ---------                     -------
> > 
> > 
> > which is different from results you have provided. Please confirm if this
> > bug can be marked Verified with the above results.
> 

Correction, what I meant to say is that this bug can be VERIFIED because the grep shows that no common class files are shared between the two manifests (which was the original problem).
Comment 7 Roshni 2016-11-04 20:28:51 UTC 
[root@mgmt3 pki]# rpm -qi pki-ca
Name        : pki-ca
Version     : 10.3.3
Release     : 13.el7_3
Architecture: noarch
Install Date: Fri 04 Nov 2016 11:51:51 AM EDT
Group       : System Environment/Daemons
Size        : 2431509
License     : GPLv2
Signature   : (none)
Source RPM  : pki-core-10.3.3-13.el7_3.src.rpm
Build Date  : Thu 03 Nov 2016 09:39:03 PM EDT
Build Host  : ppc-016.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor      : Red Hat, Inc.
URL         : http://pki.fedoraproject.org/
Summary     : Certificate System - Certificate Authority


[root@mgmt3 cert_db]# cd /usr/share/java/pki
[root@mgmt3 pki]# unzip -l pki-ca.jar > pki-ca.jar.manifest
[root@mgmt3 pki]# grep -F -x -f pki-cms.jar.manifest pki-ca.jar.manifest
grep: pki-cms.jar.manifest: No such file or directory
[root@mgmt3 pki]# unzip -l pki-ca^Car > pki-kra.jar.manifest
[root@mgmt3 pki]# unzip -l pki-kra.jar > pki-kra.jar.manifest
[root@mgmt3 pki]# unzip -l pki-ocsp.jar > pki-ocsp.jar.manifest
[root@mgmt3 pki]# unzip -l pki-tks.jar > pki-tks.jar.manifest
[root@mgmt3 pki]# unzip -l pki-tps.jar > pki-tps.jar.manifest
[root@mgmt3 pki]# unzip -l pki-cms.jar > pki-cms.jar.manifest
[root@mgmt3 pki]# grep -F -x -f pki-cms.jar.manifest pki-ca.jar.manifest
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  01-01-1980 00:00   META-INF/
        0  01-01-1980 00:00   com/
        0  01-01-1980 00:00   com/netscape/
        0  01-01-1980 00:00   org/
        0  01-01-1980 00:00   org/dogtagpki/
        0  01-01-1980 00:00   org/dogtagpki/server/
---------                     -------
[root@mgmt3 pki]# grep -F -x -f pki-cms.jar.manifest pki-kra.jar.manifest
  Length      Date    Time    Name
---------  ---------- -----   ----
      156  01-01-1980 00:00   META-INF/MANIFEST.MF
        0  01-01-1980 00:00   META-INF/
        0  01-01-1980 00:00   com/
        0  01-01-1980 00:00   com/netscape/
        0  01-01-1980 00:00   org/
        0  01-01-1980 00:00   org/dogtagpki/
        0  01-01-1980 00:00   org/dogtagpki/server/
---------                     -------
[root@mgmt3 pki]# grep -F -x -f pki-cms.jar.manifest pki-ocsp.jar.manifest
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  01-01-1980 00:00   META-INF/
        0  01-01-1980 00:00   com/
        0  01-01-1980 00:00   com/netscape/
        0  01-01-1980 00:00   org/
        0  01-01-1980 00:00   org/dogtagpki/
        0  01-01-1980 00:00   org/dogtagpki/server/
---------                     -------
[root@mgmt3 pki]# grep -F -x -f pki-cms.jar.manifest pki-tks.jar.manifest
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  01-01-1980 00:00   META-INF/
        0  01-01-1980 00:00   com/
        0  01-01-1980 00:00   com/netscape/
        0  01-01-1980 00:00   org/
        0  01-01-1980 00:00   org/dogtagpki/
        0  01-01-1980 00:00   org/dogtagpki/server/
---------                     -------
[root@mgmt3 pki]# grep -F -x -f pki-cms.jar.manifest pki-tps.jar.manifest
  Length      Date    Time    Name
---------  ---------- -----   ----
        0  01-01-1980 00:00   META-INF/
        0  01-01-1980 00:00   org/
        0  01-01-1980 00:00   org/dogtagpki/
        0  01-01-1980 00:00   org/dogtagpki/server/
---------                     -------
Comment 9 errata-xmlrpc 2016-12-06 17:04:46 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://rhn.redhat.com/errata/RHBA-2016-2881.html
Note You need to log in before you can comment on or make changes to this bug.