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.

When adding a new subsystem into an existing instance pkispawn will regenerate Tomcat configuration files such as serverCertNick.conf and server.xml. So if there are subsystem-specific settings in those files they will get replaced by the settings of the new subsystem.

For example the serverCertNick.conf on a CA may initially contain the following value:
{{{
Server-Cert cert-pki-ca
}}}

When KRA is added to the same instance it could change to this:
{{{
Server-Cert cert-pki-kra
}}}

One possible solution is to not regenerate Tomcat configuration files. This means the contents of those files are controlled by the first subsystem and if the second subsystem defines a different value it will get ignored, which may be confusing to the admin.

Another solution is to verify that the second subsystem does not define different values for the parameters that will go into Tomcat configuration files. Otherwise, the installation should fail.

Another possible solution is to split Tomcat configuration from subsystem configuration into separate deployment files. When adding a new subsystem to an existing instance only the subsystem configuration is required so the admin will not accidentally change the Tomcat configuration.

This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Verified 10.3.3:

For shared tomcat instance , files server.xml and serverCertNick.conf
are not overwritten.

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-2396.html