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.
Descriptioncilmar@redhat.com
2020-12-01 17:15:51 UTC
[DESCRIPTION OF PROBLEM]
We are facing old "ghost" or "traces" on Master (IPA02) even after uninstall and remove replicas (ipa03 and ipa04) present in the cluster.
===============================================================
Version-Release number of selected component (if applicable):
Hostname : ipa02.example.com
OS Version: Server 7.8 (Maipo) <<--Replica
Hostname : ipa04.example.com
OS Version: Server 7.9 (Maipo) <<--Master
===============================================================
[HOW REPRODUCIBLE]
We have removed ipa03 and ipa04 from IPA02 (master) using:
Remove the old replicas from IPA02:
A- REMOVE THE IPA04
# ipa-replica-manage del ipa04.example.com --force --cleanup
# ipa host-del ipa04.example.com
# ipa server-del ipa04.example.com
B- REMOVE THE IPA03
# ipa-replica-manage del ipa03.example.com --force --cleanup
# ipa host-del ipa03.example.com
# ipa server-del ipa03.example.com
===============================================================
[STEPS TO REPRODUCE]
1. Remove hosts from IPA cluster
2. List replicas using [root@ipa02 ~]# ipa-replica-manage list -v 'ipa02.example.com'
3. Check the result
===============================================================
[ACTUAL RESULTS]
[root@ipa02 ~]# ipa-replica-manage list -v 'ipa02.example.com'
ipa03.example.com: replica
last update status: Error (-1) Problem connecting to replica - LDAP error: Can't contact LDAP server (connection error)
last update ended: 1970-01-01 00:00:00+00:00
ipa04.example.com: replica
last update status: None
Traceback (most recent call last):
File "/usr/sbin/ipa-replica-manage", line 1624, in <module>
main(options, args)
File "/usr/sbin/ipa-replica-manage", line 1557, in main
options.nolookup)
File "/usr/sbin/ipa-replica-manage", line 252, in list_replicas
entry.single_value['nsds5replicalastupdateend'])))
File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 616, in __getitem__
value = self._entry[name]
File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 491, in __getitem__
return self._get_nice(name)
File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 458, in _get_nice
name = self._get_attr_name(name)
File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 454, in _get_attr_name
name = self._names[name]
File "/usr/lib/python2.7/site-packages/ipapython/ipautil.py", line 619, in __getitem__
return super(CIDict, self).__getitem__(key.lower())
KeyError: u'nsds5replicalastupdateend'
Unexpected error: u'nsds5replicalastupdateend'
==================================================================
[EXPECTED RESULT]
[root@ipa02 ~]# ipa-replica-manage list -v 'ipa02.example.com'
<Don't should be listed ipa03 and ipa04>
===================================================================
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 (ipa bug fix and enhancement update), 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-2021:4230
Comment 27Florence Blanc-Renaud
2021-11-29 14:22:43 UTC
[DESCRIPTION OF PROBLEM] We are facing old "ghost" or "traces" on Master (IPA02) even after uninstall and remove replicas (ipa03 and ipa04) present in the cluster. =============================================================== Version-Release number of selected component (if applicable): Hostname : ipa02.example.com OS Version: Server 7.8 (Maipo) <<--Replica Hostname : ipa04.example.com OS Version: Server 7.9 (Maipo) <<--Master =============================================================== [HOW REPRODUCIBLE] We have removed ipa03 and ipa04 from IPA02 (master) using: Remove the old replicas from IPA02: A- REMOVE THE IPA04 # ipa-replica-manage del ipa04.example.com --force --cleanup # ipa host-del ipa04.example.com # ipa server-del ipa04.example.com B- REMOVE THE IPA03 # ipa-replica-manage del ipa03.example.com --force --cleanup # ipa host-del ipa03.example.com # ipa server-del ipa03.example.com =============================================================== [STEPS TO REPRODUCE] 1. Remove hosts from IPA cluster 2. List replicas using [root@ipa02 ~]# ipa-replica-manage list -v 'ipa02.example.com' 3. Check the result =============================================================== [ACTUAL RESULTS] [root@ipa02 ~]# ipa-replica-manage list -v 'ipa02.example.com' ipa03.example.com: replica last update status: Error (-1) Problem connecting to replica - LDAP error: Can't contact LDAP server (connection error) last update ended: 1970-01-01 00:00:00+00:00 ipa04.example.com: replica last update status: None Traceback (most recent call last): File "/usr/sbin/ipa-replica-manage", line 1624, in <module> main(options, args) File "/usr/sbin/ipa-replica-manage", line 1557, in main options.nolookup) File "/usr/sbin/ipa-replica-manage", line 252, in list_replicas entry.single_value['nsds5replicalastupdateend']))) File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 616, in __getitem__ value = self._entry[name] File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 491, in __getitem__ return self._get_nice(name) File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 458, in _get_nice name = self._get_attr_name(name) File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 454, in _get_attr_name name = self._names[name] File "/usr/lib/python2.7/site-packages/ipapython/ipautil.py", line 619, in __getitem__ return super(CIDict, self).__getitem__(key.lower()) KeyError: u'nsds5replicalastupdateend' Unexpected error: u'nsds5replicalastupdateend' ================================================================== [EXPECTED RESULT] [root@ipa02 ~]# ipa-replica-manage list -v 'ipa02.example.com' <Don't should be listed ipa03 and ipa04> ===================================================================