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 1712794 - ERROR: invalid 'PKINIT enabled server': all masters must have IPA master role enabled
Summary: ERROR: invalid 'PKINIT enabled server': all masters must have IPA master role...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.6
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks: 1712797 1716882
TreeView+ depends on / blocked
 
Reported: 2019-05-22 09:22 UTC by Ron van der Wees
Modified: 2019-08-06 13:09 UTC (History)
12 users (show)

Fixed In Version: ipa-4.6.5-9.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1712797 1716882 (view as bug list)
Environment:
Last Closed: 2019-08-06 13:09:47 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2241 0 None None None 2019-08-06 13:09:54 UTC

Description Ron van der Wees 2019-05-22 09:22:15 UTC 
Description of problem:
If a replica installation fails before all the services have been enabled then
it could leave things in a bad state.
~~~
Joining realm failed: RPC failed at server.  invalid 'PKINIT enabled server': all masters must have IPA master role enabled
~~~

Version-Release number of selected component (if applicable):
ipa-server-4.6.4-10.el7_6.3.x86_64.rpm


How reproducible:
Always


Steps to Reproduce:
1. Install a new replica on RHEL7.6 while the master is older
2.
3.


Actual results:
Due to NSSCipherSuite line in /etc/httpd/conf.d/nss.conf installing the new
replica fails and it lot possible to remove the replica:
~~~
ipa-replica-manage del <replica> --cleanup --force
invalid 'PKINIT enabled server': all masters must have IPA master role enabled
~~~


Expected results:
Be able to remove the replica.


Additional info:
Bugzilla created to track backport of upstream fix:
https://pagure.io/freeipa/issue/7929
Comment 1 Rob Crittenden 2019-05-22 13:23:16 UTC 
Upstream ticket:
https://pagure.io/freeipa/issue/7929
Comment 5 Florence Blanc-Renaud 2019-06-04 10:00:38 UTC 
Fixed upstream:
master:
    https://pagure.io/freeipa/c/3c9818798892e70d53048537a0c8dadb878d8652 Consider configured servers as valid

ipa-4-7:
    https://pagure.io/freeipa/c/7b63b88d5b656c629bec137e55029f3812130199 Consider configured servers as valid

ipa-4-6:
    https://pagure.io/freeipa/c/2f9793cc6111dd2de8ae44adf8a446331c6811f8 Consider configured servers as valid
Comment 8 Nikhil Dehadrai 2019-06-25 10:18:22 UTC 
IPA: ipa-server-4.6.5-9.el7.x86_64

Verified the bug on the basis of following observations:

Steps:
1) install server
2) install replica
3) modify the replica entry on Master:
ldapmodify -D cn=directory\ manager -w <passwd>
dn: cn=KDC,cn=<replicaFQDN>,cn=masters,cn=ipa,cn=etc,<baseDN>
changetype: modify
replace: ipaconfigstring
ipaconfigstring: pkinitEnabled
ipaconfigstring: configuredService
4) on master, run ipa-replica-manage del <replicaFQDN> --cleanup --force

REPRODUCER:
===========
(On Master)
[root@vm-idm-023 tmp]# rpm -q ipa-server
ipa-server-4.6.4-10.el7_6.3.x86_64
[root@vm-idm-023 tmp]# cat /tmp/test.ldif 
dn: cn=KDC,cn=vm-idm-017.testrelm.test,cn=masters,cn=ipa,cn=etc,dc=testrelm, dc=test
changetype: modify
replace: ipaconfigstring
ipaconfigstring: pkinitEnabled
ipaconfigstring: configuredService
[root@vm-idm-023 tmp]# ldapmodify -D cn=directory\ manager -w Secret123 -f  test.ldif 
modifying entry "cn=KDC,cn=vm-idm-017.testrelm.test,cn=masters,cn=ipa,cn=etc,dc=testrelm, dc=test"
[root@vm-idm-023 tmp]# ipa-replica-manage del vm-idm-017.testrelm.test
invalid 'PKINIT enabled server': all masters must have IPA master role enabled

Verification:
=============
(On Master)
[root@qe-blade-01 tmp]# rpm -q ipa-server
ipa-server-4.6.5-9.el7.x86_64
[root@qe-blade-01 tmp]# cat /tmp/test.ldif 
dn: cn=KDC,cn=qe-blade-04.testrelm.test,cn=masters,cn=ipa,cn=etc,dc=testrelm, dc=test
changetype: modify
replace: ipaconfigstring
ipaconfigstring: pkinitEnabled
ipaconfigstring: configuredService
[root@qe-blade-01 tmp]# ldapmodify -D cn=directory\ manager -w Secret123 -f  test.ldif
modifying entry "cn=KDC,cn=qe-blade-04.testrelm.test,cn=masters,cn=ipa,cn=etc,dc=testrelm, dc=test"
[root@qe-blade-01 tmp]# ipa-replica-manage del qe-blade-04.testrelm.test
Updating DNS system records
----------------------------------------------
Deleted IPA server "qe-blade-04.testrelm.test"
----------------------------------------------
[root@qe-blade-01 tmp]#


Thus on the basis of above observations, marking bug to 'VERIFIED'
Comment 11 errata-xmlrpc 2019-08-06 13:09:47 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:2241
Note You need to log in before you can comment on or make changes to this bug.