Installed fresh Fedora 21 alpha + updates-testing, then installed 'freeipa-server' and tried to configure FreeIPA. Dogtag fails due to selinux issues (a separate bug will be filed) when making a backup of CS.cfg file on dogtag startup and it exposes syntax errors in /usr/share/pki/scripts/operations shell script. There are multiple places in the script where a following idiom is used: $((backup_errors++)) this construction is invalid from bash syntax perspective as bash will try to execute result of arithmetic operation. As result, the script never finishes correctly. This makes impossible to configure FreeIPA server in Fedora 21.
The actual error messages in journaldb are the following: Sep 30 13:06:04 cc21.ipacloud.test pkidaemon[2956]: cp: cannot create regular file </var/lib/pki/pki-tomcat/conf/ca/archives/CS.cfg.bak.20140930130604: Permission denied Sep 30 13:06:04 cc21.ipacloud.test pkidaemon[2956]: WARNING: Failed to archive '/var/lib/pki/pki-tomcat/conf/ca/CS.cfg' to '/var/lib/pki/pki-tomcat/conf/ca/archives/CS.cfg.bak.20140930130604'! Sep 30 13:06:04 cc21.ipacloud.test pkidaemon[2956]: /usr/share/pki/scripts/operations: line 1564: 0: command not found Sep 30 13:06:04 cc21.ipacloud.test systemd[1]: pki-tomcatd: control process exited, code=exited status=1 Sep 30 13:06:04 cc21.ipacloud.test systemd[1]: Failed to start PKI Tomcat Server pki-tomcat.
I suspect that the SELinux AVCs you encountered are the same as bug 1117673.
Ignore SELinux AVCs, I've already gave karma to selinux-policy update. However, syntax errors need to be fixed.
Syntax changes commited to the following branches: * master (0b6cfad8f1c566bc296ee8bd8be8b84e14b31ae6) and then cherry-picked to the following branches: * DOGTAG_10_2_0_BRANCH (eee5112a414195bcb6185dd7a49ffd2b80756110) * DOGTAG_10_2_RHEL_BRANCH (f20f8e83384348dfb7cf1b7b0203747e335b2c8f)
Note that although the fixes for this bug were checked into the DOGTAG_10_2_0_BRANCH (Fedora 21), no new builds have been construced; however, the fix for this issue does reside inside the build for Fedora 22.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.