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.
Summary:
There is an issue with the symlinks to jars during upgrade from different versions
Alexander Bokovoy did fix this for Fedora with F16 release in past -- in /usr/libexec/freeipa-systemd-update in Fedora packages there is an elaborate code to handle these updates of the symlinks.
We need to extract that part and add to RHEL6.
For more details see mail thread:
https://www.redhat.com/archives/freeipa-users/2012-September/msg00006.html
This is not an IPA problem, we simply recognize it during upgrade and attempt to fix it in Fedora (when we fix other things, such as converting from SysV to systemd).
The problem seems to be that on 64-bit platforms the symlink for jss was in /usr/lib and not in /usr/lib64 and this caused dogtag to not start.
I think this bug should be re-pointed to either dogtag or jss and should not be fixed by IPA.
As it is not an IPA problem I am closing this BZ.
Other BZs will be open against the corresponding java packages that cause the problem in the first place.