See bug 1129558, comment 3 for a workaround.
Alternative workaround would be to manually create an AD-compatible CSR:
# echo -e -n '\x1E\x0A\x00\x53\x00\x75\x00\x62\x00\x43\x00\x41' >ext-value
# certutil -R -d /etc/pki/pki-tomcat/alias -f <(grep -Po '(?<=internal=).*' /etc/pki/pki-tomcat/password.conf) -k 'caSigningCert cert-pki-ca' --extGeneric=220.127.116.11.4.1.311.20.2:not-critical:ext-value -o ipa.csr -a
From Thorsten: The issue reported by the customer (CA installed on replica is always configured as renewal master) has been fixed with this errata:
In c#225 the customer mentioned, that they do their installs using a RHEL-7.2 DVD image. The fix has been released for RHEL-7.3 and as an async update for RHEL-7.2.z. It's not part of RHEL-7.2 GA release though. This means, they need to install at least the following package to get rid of the issue: ipa-4.2.0-15.el7_2.17. (or later).
See this BZ for details:
CA installed on replica is always marked as renewal master
From customer: That bugzilla does appear to describe the behavior. As both projects (using 7.1 and 7.2 respectively) are in a phase where package updates are not possible, is running "ipa-csreplica-manage set-renewal-master" on the master a viable workaround? It has corrected the LDAP entries every time I've run it, and the CS.cfg files on the master and replica already appear to be okay. Are there any other parts related to this that were fixed that require the updated packages?
Verified on RHEL7.4 using
Attaching the steps used for verification.
Created attachment 1279705 [details]
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.