#9337 Nightly test failure (testing_master_pki): Server installation is failing for CA configuration.
Closed: fixed by frenaud. Opened by amore.

The nightly tests detected a regression when using the nightly build of pki master branch.

The regression was seen with PR #2470, with the following logs and report:
ipa-server install is failing with error:

DEBUG    ipatests.pytest_ipa.integration.host.Host.master.cmd38:transport.py:557   [5/5]: configuring ipa-custodia to start on boot
DEBUG    ipatests.pytest_ipa.integration.host.Host.master.cmd38:transport.py:557 Done configuring ipa-custodia.
DEBUG    ipatests.pytest_ipa.integration.host.Host.master.cmd38:transport.py:557 Configuring certificate server (pki-tomcatd). Estimated time: 3 minutes
DEBUG    ipatests.pytest_ipa.integration.host.Host.master.cmd38:transport.py:557   [1/30]: configuring certificate server instance
DEBUG    ipatests.pytest_ipa.integration.host.Host.master.cmd38:transport.py:557 Failed to configure CA instance
DEBUG    ipatests.pytest_ipa.integration.host.Host.master.cmd38:transport.py:557 See the installation logs and the following files/directories for more information:
DEBUG    ipatests.pytest_ipa.integration.host.Host.master.cmd38:transport.py:557   /var/log/pki/pki-tomcat
DEBUG    ipatests.pytest_ipa.integration.host.Host.master.cmd38:transport.py:557   [error] RuntimeError: CA configuration failed.
DEBUG    ipatests.pytest_ipa.integration.host.Host.master.cmd38:transport.py:557 CA configuration failed.
DEBUG    ipatests.pytest_ipa.integration.host.Host.master.cmd38:transport.py:557 The ipa-server-install command failed. See /var/log/ipaserver-install.log for more information

Metadata Update from @amore:
- Issue tagged with: test-failure, testblocker, tracker

Companion issue opened against pki: https://github.com/dogtagpki/pki/issues/4339

Hi @frenaud, to help track down, when was the last successful run?

I think I have resolved the issue. Some modifications were made to Tomcat configuration (removed permissions). Restoring some of the permissions fixes the problem see: https://github.com/dogtagpki/pki/pull/4341

Issue has been solved by pki as we can see in the latest nightly run: PR #2487: Details

The issue was only present on pki master branch, no need to bump pki version in our spec file. Closing as fixed.

Metadata Update from @frenaud:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

Metadata