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.
DescriptionRon van der Wees
2019-05-22 09:25:16 UTC
+++ This bug was initially created as a clone of Bug #1712794 +++
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
Marking the bug verified as per the below steps and observations
ipa-server-4.8.0-6.module+el8.1.0+3869+84a20141.x86_64
ipa-server-dns-4.8.0-6.module+el8.1.0+3869+84a20141.noarch
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
[root@master ~]# ipa-replica-manage del replica.rhel81.test
Updating DNS system records
ipa: WARNING: Failed to cleanup replica.rhel81.test DNS entries: no matching entry found
ipa: WARNING: You may need to manually remove them from the tree
----------------------------------------
Deleted IPA server "replica.rhel81.test"
----------------------------------------
[root@master ~]# ipa-replica-manage del replica.rhel81.test --cleanup --force
Updating DNS system records
ipa: WARNING: Forcing removal of replica.rhel81.test
ipa: WARNING: Ignoring topology connectivity errors.
ipa: WARNING: Failed to cleanup replica.rhel81.test DNS entries: no matching entry found
ipa: WARNING: You may need to manually remove them from the tree
ipa: WARNING: Server has already been deleted
----------------------------------------
Deleted IPA server "replica.rhel81.test"
----------------------------------------
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:3348