#8605 backtrace using ipa-replica-manage
Closed: fixed 3 years ago by frenaud. Opened 3 years ago by fcami.

Ticket was cloned from Red Hat Bugzilla: Bug 1903250

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

[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>
===================================================================

Metadata Update from @fcami:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1903250

3 years ago

Metadata Update from @fcami:
- Custom field on_review adjusted to https://github.com/freeipa/freeipa/pull/5313

3 years ago

Metadata Update from @fcami:
- Issue assigned to fcami

3 years ago

master:

  • 4b2c50a ipa-replica-manage: always display nsds5replicalastinitstatus
  • bc3906f ipa-replica-manage: handle missing attributes
  • 82e3243 ipalib/util.py: add print_replication_status
  • 216720a ipa-csreplica-manage, ipa-replica-manage: refactor

ipa-4-9:

  • f6204b0 ipa-replica-manage: always display nsds5replicalastinitstatus
  • 85484d3 ipa-replica-manage: handle missing attributes
  • 5f2f97a ipalib/util.py: add print_replication_status
  • 25cbae4 ipa-csreplica-manage, ipa-replica-manage: refactor

Metadata Update from @frenaud:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

3 years ago

master:

  • f1a4418 Extend test to see if replica is not shown when running ipa-replica-manage list -v <FQDN>

ipa-4-9:

  • 8b22ee0 Extend test to see if replica is not shown when running ipa-replica-manage list -v <FQDN>

Login to comment on this ticket.

Metadata