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.

Created attachment 1614229 [details]
From /var/log/pki/pki-tomcat/ca/debug

Description of problem:
If ipa-server and ipa-server-dns are installed using yum on a RHEL 7.6 system, which does not have the os release version set, or has the os release version set to 7Server, ipa-server-install will fail.

Version-Release number of selected component (if applicable):
ipa-server-4.6.5-11.el7.x86_64

How reproducible:
Every time

Steps to Reproduce:
1. Confirm that the system is running RHEL 7.6 (cat /etc/redhat-release)
2. Confirm that the os release version is not set, or set to 7Server (subscription-manager release --show)
3. yum install ipa-server ipa-server-dns
4. Check if the system needs to reboot (needs-restarting -r). Reboot if needed.
5. ipa-server-install

Actual results:
Install fails with the error "The ipa-server-install command failed, exception: RuntimeError: CA did not start in 300.0s"


Expected results:
Install completes successfully

Additional info:
excerpt from install log and pki ca debug log attached.

Created attachment 1614230 [details]
From ipa install log

Can you provide the full logs instead of just the snippets?

As far as I know, the version of ipa-server shipped with RHEL 7.6 is ipa-4.6.4-10.el7, but the BZ is mentioning ipa-server-4.6.5-11.el7.x86_64 (shipped with RHEL 7.7). The recommendation is to upgrade the whole system to 7.7 in order to use the bits from ipa-server 4.6.5-11.

Created attachment 1614520 [details]
Complete Install Log

I reproduced the error on a generic system, and attached the complete install logs as requested.

Updating the system to 7.7 does result in a successful install.
Setting the OS release version to 7.6 (subscription-manager release --set 7.6) BEFORE yum install ipa-server also results in a successful install.

This bug is suggesting that it should not be possible to install mismatched packages, which result in a failed ipa-server-install.

Installing mixed packages in RHEL is not tested. This is not something that IPA can enforce.

I am afraid, we should close this BZ. Explanation is provided in Comment 7.