Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1716882

Summary: ERROR: invalid 'PKINIT enabled server': all masters must have IPA master role enabled [rhel-7.6.z]
Product: Red Hat Enterprise Linux 7 Reporter: RAD team bot copy to z-stream <autobot-eus-copy>
Component: ipaAssignee: IPA Maintainers <ipa-maint>
Status: CLOSED ERRATA QA Contact: ipa-qe <ipa-qe>
Severity: medium Docs Contact:
Priority: high    
Version: 7.6CC: afarley, amarecek, cobrown, frenaud, ipa-maint, msauton, ndehadra, pvoborni, rcritten, rvdwees, ssidhaye, tmihinto, toneata, tscherf
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: ipa-4.6.4-10.el7_6.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1712794 Environment:
Last Closed: 2019-07-29 15:14:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1712794    
Bug Blocks:    

Description RAD team bot copy to z-stream 2019-06-04 10:53:57 UTC
This bug has been copied from bug #1712794 and has been proposed to be backported to 7.6 z-stream (EUS).

Comment 3 Sumedh Sidhaye 2019-07-12 08:53:03 UTC
[root@spider ~]# cat test.sh 
rpm -q ipa-server
cat test.ldif
ldapmodify -D cn=directory\ manager -w Secret123 -f  test.ldif
ipa-replica-manage del replica.testrelm.test --cleanup --force

[root@spider ~]# 



[root@spider ~]# ./test.sh 
ipa-server-4.6.4-10.el7_6.6.x86_64
dn: cn=KDC,cn=replica.testrelm.test,cn=masters,cn=ipa,cn=etc,dc=testrelm, dc=test
changetype: modify
replace: ipaconfigstring
ipaconfigstring: pkinitEnabled
ipaconfigstring: configuredService
modifying entry "cn=KDC,cn=replica.testrelm.test,cn=masters,cn=ipa,cn=etc,dc=testrelm, dc=test"

Directory Manager password: 

Updating DNS system records
ipa: WARNING: Forcing removal of replica.testrelm.test
ipa: WARNING: Ignoring topology connectivity errors.
ipa: WARNING: Failed to cleanup replica.testrelm.test DNS entries: no matching entry found
ipa: WARNING: You may need to manually remove them from the tree
------------------------------------------
Deleted IPA server "replica.testrelm.test"
------------------------------------------

Comment 7 errata-xmlrpc 2019-07-29 15:14:17 UTC
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://access.redhat.com/errata/RHBA-2019:1889