The IdM CA service now starts correctly on IPv6-only installations
Previously, on systems only configured for IPv6, the *pki-tomcat* service was incorrectly bound to the IPv4 loopback device during Identity Management (IdM) installation. As a consequence, the certificate authority (CA) service failed to start. The IdM setup now binds on systems having only the IPv6 protocol configured, to the IPv6 loopback device. As a result, the CA service starts correctly.
fixed by alee:
Added option to pkispawn to add pki_ajp_host in the tomcat section.
Delta compression using up to 8 threads. Compressing objects: 100% (27/27), done. Writing objects: 100% (33/33), 7.41 KiB | 0 bytes/s, done. Total 33 (delta 18), reused 0 (delta 0) To ​ssh://vakwetu.org/git/pki.git
Checked into master:
* d77c0f15ad4d51af998b7ab89f7482b7d0b3a370
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2016-2396.html