Bug 1903250 - backtrace using ipa-replica-manage
Summary: backtrace using ipa-replica-manage
Keywords:
Status: POST
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.3
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: rc
: 8.4
Assignee: François Cami
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-01 17:15 UTC by cilmar@redhat.com
Modified: 2021-04-21 20:04 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description cilmar@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>
===================================================================

Comment 2 François Cami 2020-12-02 08:54:59 UTC
Upstream ticket:
https://pagure.io/freeipa/issue/8605

Comment 4 François Cami 2020-12-15 14:07:10 UTC
Moving to RHEL 8.
If a fix for this backtrace is needed for RHEL 7, please clone this bug.


Note You need to log in before you can comment on or make changes to this bug.