https://bugzilla.redhat.com/show_bug.cgi?id=1348946 seems to have been fixed in current Rawhide, but FreeIPA server deployment is still failing. Here's today's openQA attempt:
https://openqa.fedoraproject.org/tests/24638
You can find the contents of /var/log here:
https://openqa.fedoraproject.org/tests/24638/file/role_deploy_domain_controller -var_log.tar.gz Looking through the logs, I see this in ipaserver-install.log: 2016-07-04T12:42:14Z DEBUG stdout=Log file: /var/log/pki/pki-ca-spawn.20160704084213.log Loading deployment configuration from /tmp/tmp1X2EK4. Installing CA into /var/lib/pki/pki-tomcat. Storing deployment configuration into /etc/sysconfig/pki/tomcat/pki-tomcat/ca/deployment.cfg. Installation failed: Dangling symlink /var/lib/pki/pki-tomcat/common/lib/scannotation.jar not allowed 2016-07-04T12:42:14Z DEBUG stderr=pkispawn : WARNING ....... Dangling symlink '/var/lib/pki/pki-tomcat/common/lib/scannotation.jar'-->'/usr/share/jav a/scannotation.jar' 2016-07-04T12:42:14Z CRITICAL Failed to configure CA instance: Command '/usr/sbin/pkispawn -s CA -f /tmp/tmp1X2EK4' returned non-zero exit status 1 2016-07-04T12:42:14Z CRITICAL See the installation logs and the following files/directories for more information: 2016-07-04T12:42:14Z CRITICAL /var/log/pki/pki-tomcat 2016-07-04T12:42:14Z DEBUG Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ipaserver/install/service.py", line 447, in start_creation run_step(full_msg, method) File "/usr/lib/python2.7/site-packages/ipaserver/install/service.py", line 437, in run_step method() File "/usr/lib/python2.7/site-packages/ipaserver/install/cainstance.py", line 579, in __spawn_instance DogtagInstance.spawn_instance(self, cfg_file) File "/usr/lib/python2.7/site-packages/ipaserver/install/dogtaginstance.py", line 181, in spawn_instance self.handle_setup_error(e) File "/usr/lib/python2.7/site-packages/ipaserver/install/dogtaginstance.py", line 421, in handle_setup_error raise RuntimeError("%s configuration failed." % self.subsystem) RuntimeError: CA configuration failed. /usr/share/java/scannotation.jar appears to be part of the 'scannotation' package. Looking at /var/log/dnf.rpm.log from the test I don't see any indication that this package was installed, which may be the problem.
proposing as an F25 Alpha blocker - "Release-blocking roles and the supported role configuration interfaces must meet the core functional Role Definition Requirements to the extent that supported roles can be successfully deployed, started, stopped, brought to a working configuration, and queried." (you can't deploy the domain controller role because of this).
If I install scannotation package manually before attempting the role deployment, I get a different dangling symlink:
Installation failed: Dangling symlink /var/lib/pki/pki-tomcat/common/lib/jaxrs-api.jar not allowed 2016-07-07T00:32:41Z DEBUG stderr=pkispawn : WARNING ....... Dangling symlink '/var/lib/pki/pki-tomcat/common/lib/ jaxrs-api.jar'-->'/usr/share/java/resteasy/jaxrs-api.jar'
In F24, this file is part of the package resteasy-jaxrs-api . In F25, it apparently is not - it doesn't seem to be part of anything, according to repoquery -f on a Rawhide box.
Per PKI Bug Council of 07/14/2016: 10.3.5
Assigned to vakwetu for investigation
Fixed in master:
Additional changes in master:
The problem happens both in F24 and F25.
hi
/usr/share/java/resteasy/jaxrs-api.jar is no more available.
please, use instead jboss-jaxrs-2.0-api
soon should be available also in F24 https://bodhi.fedoraproject.org/updates/FEDORA-2016-3aee3bf66c
regards
Yes, Fedora 24 or later will use /usr/share/java/jboss-jaxrs-2.0-api.jar.
Metadata Update from @awilliam: - Issue assigned to edewata - Issue set to the milestone: 10.3.5
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2523
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Log in to comment on this ticket.