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.
There is a mismatch between the version of the symkey.jar links/files and the rpm.
$ ls -l /usr/lib/java/symkey.jar
lrwxrwxrwx. 1 root root 26 Jan 20 20:53 /usr/lib/java/symkey.jar -> /usr/lib/symkey/symkey.jar
$ ls -l /usr/lib/symkey/symkey.jar
lrwxrwxrwx. 1 root root 16 Jan 20 20:53 /usr/lib/symkey/symkey.jar -> symkey-9.0.1.jar
$ ls /usr/lib/symkey/symkey*
symkey-9.0.0.jar symkey.jar
$ rpm -qf /usr/lib/symkey/symkey-9.0.0.jar
pki-symkey-9.0.1-1.svn.1757M.20110120T1814z.fc14.i686
Note that actual jar file is /usr/lib/symkey/symkey-9.0.0.jar but the link points to symkey-9.0.1.jar.
FWIW, the rpm is pki-symkey-9.0.1
The dangling symlink causes symkey.jar to not be found by pkicreate, which then aborts an installation.
Not exactly sure if this verifies this issue ... but the installations are working fine. Can development comment?
ls -l /usr/lib/java/symkey.jar
lrwxrwxrwx. 1 root root 28 Apr 14 15:31 /usr/lib/java/symkey.jar -> /usr/lib64/symkey/symkey.jar
# ls /usr/lib64/symkey/symkey*
/usr/lib64/symkey/symkey-9.0.3.jar /usr/lib64/symkey/symkey.jar
# rpm -qf /usr/lib64/symkey/symkey-9.0.3.jar
pki-symkey-9.0.3-10.el6.x86_64
# rpm -qf /usr/lib64/symkey/symkey.jar
pki-symkey-9.0.3-10.el6.x86_64
Versions:
pki-ca-9.0.3-10.el6.noarch
ipa-server-2.0.0-21.el6.x86_64
One more and verified!
# rpm -ql pki-symkey
/usr/lib/java/symkey.jar
/usr/lib64/symkey
/usr/lib64/symkey/libsymkey.so
/usr/lib64/symkey/symkey-9.0.3.jar
/usr/lib64/symkey/symkey.jar
/usr/share/doc/pki-symkey-9.0.3
/usr/share/doc/pki-symkey-9.0.3/LICENSE
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHEA-2011-0627.html