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.
Description of problem:
This is a possible regression of https://bugzilla.redhat.com/show_bug.cgi?id=826677
Initial topology: (single replication)
1
|
2
Version-Release number of selected component (if applicable):
ipa-server-3.3.1-1.el7.x86_64
How reproducible:
alweays
Steps to Reproduce:
#. on host 1
1. ipa-server-install
2. ipa-replica-prepare --ip-address=<ip of host 2> host2
#. on host 2
3. ipa-replica-install <gpg-file>
#. on host 1
4. ipa-replica-manage disconnect $HOST1 $HOST2
# on host2:
5. ipa-server-install --uninstall -U
# on host1:
5. ipa-replica-prepare -p $ADMINPW --ip-address=$HOST2_IP $HOST2
# on host2:
6. cd /dev/shm; sftp root@$HOST1:/var/lib/ipa/replica-info-$HOST2.gpg
7. ipa-replica-install -U --setup-dns --forwarder=$DNSFORWARD -w $ADMINPW -p $ADMINPW /dev/shm/replica-info-$HOST2.gpg
Actual results:
[root@ipaqavme ~]# ipa host-del --updatedns ipaqavmf.testrelm.com
ipa: ERROR: invalid 'hostname': An IPA master host cannot be deleted or disabled
[root@ipaqavme ~]# ipa-replica-manage del ipaqavmf.testrelm.com --force
Connection to 'ipaqavmf.testrelm.com' failed:
Forcing removal of ipaqavmf.testrelm.com
Skipping calculation to determine if one or more masters would be orphaned.
No RUV records found.
[root@ipaqavme ~]# ipa host-del --updatedns ipaqavmf.testrelm.com
ipa: ERROR: invalid 'hostname': An IPA master host cannot be deleted or disabled
Additional info:
I am able to work-around this problem by following the instructions noted in comment 15 from BZ 826677, ith this command:
[root@ipaqavme ~]# ldapdelete -r -x -D "cn=Directory Manager" -W 'cn=ipaqavmf.testrelm.com,cn=masters,cn=ipa,cn=etc,dc=testrelm,dc=com'
Enter LDAP Password:
[root@ipaqavme ~]# ldapsearch -x -LLL -D "cn=Directory Manager" -W -b 'cn=ipaqavmf.testrelm.com,cn=masters,cn=ipa,cn=etc,dc=testrelm,dc=com'
Enter LDAP Password:
No such object (32)
Matched DN: cn=masters,cn=ipa,cn=etc,dc=testrelm,dc=com
I am still getting this error, do I not have the updated bits? I am currently on ipa-server-3.3.1-1.el7.x86_64:
[root@tigger ipa-dns-multi]# ipa-replica-manage del ipaqa64vmg.testrelm2.com --cleanup
Connection to 'ipaqa64vmg.testrelm2.com' failed:
Forcing removal of ipaqa64vmg.testrelm2.com
Skipping calculation to determine if one or more masters would be orphaned.
No RUV records found.
[root@tigger ipa-dns-multi]# ipa host-del --updatedns ipaqa64vmg.testrelm2.com
ipa: ERROR: invalid 'hostname': An IPA master host cannot be deleted or disabled
Previous RHEL build did not contain the patch - I produced a new one (ipa-3.3.1-2.el7) which should fix this issue.
Closing as duplicate for Bug 1001662, please write a note there if the fix does not work.
*** This bug has been marked as a duplicate of bug 1001662 ***