#2804 ipa-csreplica-manage connect/disconnect options provide inconsistent results
Closed: wontfix 5 years ago Opened 11 years ago by rcritten.

https://bugzilla.redhat.com/show_bug.cgi?id=827489 (Red Hat Enterprise Linux 6)

Here is the test scenario:
-----------------------------------------------------------------------------
Master -- neptune ; Replica-1 -- mars ; Replica-2 -- silverbolt ; Replica-3 --
uranus
-----------------------------------------------------------------------------
1] Create Master (neptune)
1.1] Create replica files for Replica-1(mars) and Replica-2(silverbolt). And
scp them to
respective machines.

2] On Replica-1(mars): Do a replica install *without* '--setup-ca'

3] On Replica-2(silverbolt): Do a replica install with '--setup-ca'
3.1] Generate a replica file on Replica-2 for Replica-3(uranus)

4] On Replica-3(uranus): Do a replica install with '--setup-ca'
-----------------------------------------------------------------------------

This test is between Replica-2(silverbolt) and Replica-3(uranus):

-> list the agreemtns on Replica-2
=====================
[root@silverbolt slapd-LAB-ENG-PNQ-REDHAT-COM]# ipa-csreplica-manage list -p
Secret123
silverbolt.lab.eng.pnq.redhat.com
neptune.lab.eng.pnq.redhat.com
uranus.lab.eng.pnq.redhat.com
=====================

-> Let's do a 'connect' purposefully  (also note: the --verbose doesn't provide
any extra
info) on uranus(Replica3)
=====================
[root@uranus ~]# ipa-csreplica-manage --verbose -p Secret123 connect
silverbolt.lab.eng.pnq.redhat.com uranus.lab.eng.pnq.redhat.com
This replication agreement already exists.
=====================

-> Since the replication agreement already exists, let's try to 'disconnect'
it. Deleted.
Expected.
=====================
[root@uranus ~]# ipa-csreplica-manage --verbose -p Secret123 disconnect
silverbolt.lab.eng.pnq.redhat.com uranus.lab.eng.pnq.redhat.com
Deleted replication agreement from 'silverbolt.lab.eng.pnq.redhat.com' to
'uranus.lab.eng.pnq.redhat.com'
=====================

-> Let's try to list the agreements of uranus. None. Expected.
=====================
[root@uranus ~]# ipa-csreplica-manage list -p Secret123
uranus.lab.eng.pnq.redhat.com
=====================
[root@uranus ~]# ipa-csreplica-manage --verbose list -p Secret123
uranus.lab.eng.pnq.redhat.com
[root@uranus ~]#
=====================

-> Now, let's try to 'connect' again (since we've disconnected it previously).
But here:
it says the 'replication agreement already exists' . How?
=====================
[root@uranus ~]# ipa-csreplica-manage --verbose -p Secret123 connect
silverbolt.lab.eng.pnq.redhat.com uranus.lab.eng.pnq.redhat.com
This replication agreement already exists.
[root@uranus ~]#
=====================

-> Since it says replication agreement exists in the previous command, let's
try to
disconnect *again* :
=====================
[root@uranus ~]# ipa-csreplica-manage --verbose -p Secret123 disconnect
silverbolt.lab.eng.pnq.redhat.com uranus.lab.eng.pnq.redhat.com
Cannot remove the last replication link of 'silverbolt.lab.eng.pnq.redhat.com'
Please use the 'del' command to remove it from the domain
[root@uranus ~]#
=====================

-> let's list all the servers for replication on 'uranus'(Replica-3)
=====================
[root@uranus ~]# ipa-csreplica-manage --verbose list -p Secret123
mars.lab.eng.pnq.redhat.com: CA not configured
neptune.lab.eng.pnq.redhat.com: master
silverbolt.lab.eng.pnq.redhat.com: master
uranus.lab.eng.pnq.redhat.com: master
[root@uranus ~]#
=====================

Releasing tickets from distant milestones.

Metadata Update from @rcritten:
- Issue assigned to someone
- Issue set to the milestone: Future Releases

7 years ago

Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.

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

5 years ago

Login to comment on this ticket.

Metadata