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.
Bug 1366612 - Middle replica uninstallation in line topology works without '--ignore-topology-disconnect'
Summary: Middle replica uninstallation in line topology works without '--ignore-topolo...
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Kaleem
Depends On: 1376723
TreeView+ depends on / blocked
Reported: 2016-08-12 12:46 UTC by Petr Vobornik
Modified: 2016-11-04 06:00 UTC (History)
5 users (show)

Fixed In Version: ipa-4.4.0-8.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-11-04 06:00:57 UTC
Target Upstream Version:

Attachments (Terms of Use)
console.log (2.38 KB, text/plain)
2016-09-20 05:16 UTC, Abhijeet Kasurde
no flags Details

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2404 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2016-11-03 13:56:18 UTC

Description Petr Vobornik 2016-08-12 12:46:39 UTC
This bug is created as a clone of upstream ticket:

I was able to uninstall the middle replica in line topology using 'ipa-server-install --uninstall' without specifying '--ignore-topology-disconnect'. [[BR]]
Topology looks like this:
master <-> replica1 <-> replica2

Replica1 was uninstalled successfully.
After replica uninstallation, the output of 'ipa topologysegment-find domain' did not change and looked like:
2 segments matched
  Segment name: replica2-to-replica1
  Left node: replica2
  Right node: replica1
  Connectivity: both

  Segment name: master-to-replica1
  Left node: master
  Right node: replica1
  Connectivity: both
Number of entries returned 2

The version of the freeipa packages is

Expected behavior:

Uninstallation should fail and an error message should be displayed:
"Uninstallation leads to disconnected topology"

Comment 1 Petr Vobornik 2016-08-12 12:48:11 UTC
Related to replica promotion and topology management RFEs

Comment 2 Martin Babinsky 2016-08-17 12:59:43 UTC
Fixed upstream

Comment 4 Abhijeet Kasurde 2016-09-20 05:15:53 UTC
Verified using IPA version::

Marking BZ as verified.

Comment 5 Abhijeet Kasurde 2016-09-20 05:16:15 UTC
Created attachment 1202692 [details]

Comment 7 errata-xmlrpc 2016-11-04 06:00:57 UTC
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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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