The error thrown is:

###################################################
                ##Installing CA into /var/lib/pki/pki-subca.##
                ##Storing deployment configuration into /etc/sysconfig/pki/tomcat/pki-subca/ca/deployment.cfg.##
                ##Traceback (most recent call last):##
                ##File "/usr/lib64/python2.7/logging/__init__.py", line 851, in emit##
                ##msg = self.format(record)##
                ##File "/usr/lib64/python2.7/logging/__init__.py", line 724, in format##
                ##return fmt.format(record)##
                ##File "/usr/lib64/python2.7/logging/__init__.py", line 467, in format##
                ##s = self._fmt % record.__dict__##
                ##KeyError: 'indent'##
                ##Logged from file selinux_setup.py, line 133##

Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog

Per 10.2.3 TRIAGE meeting of 02/26/2015: 10.3

NOTE: Moved from 10.2 Backlog since it was not a documentation/man page issue.

Is it really just a check for pki_http_port != pki_https_port or should the check be extended to all ports? I found this port definitions:

• pki_ajp_port=8009
• pki_authdb_port=389
• pki_clone_replication_clone_port=
• pki_clone_replication_master_port=
• pki_ds_ldap_port=389
• pki_ds_ldaps_port=636
• pki_http_port=8080
• pki_https_port=8443
• pki_proxy_http_port=80
• pki_proxy_https_port=443
• pki_security_domain_https_port=8443
• pki_tomcat_server_port=8005

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/1748

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.