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.

Description of problem:
If user tries to delete middle replica in line topology, then Server removal error is thrown. This error should also advertise about available '--ignore-topology-disconnect' which overrides this check.

Version-Release number of selected component (if applicable):
ipa-server-4.4.0-12.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. try to delete middle replica in line topology

Actual results:
Error message is correct, but doesn't suggest anything to override this behavior

Expected results:
Server removal error should advertise about '--ignore-topology-disconnect' option

AFAIK it was not added there on purpose.

Removal of middle replica should not happen in normal circumstances. Advertising the option may lead to blindly copying of it without thinking about consequences. Recovering from such act may not be trivial.

If one gets to this situation, he should change topology first. The error should suggest that.

(In reply to Petr Vobornik from comment #2)
> AFAIK it was not added there on purpose.
> 
> Removal of middle replica should not happen in normal circumstances.
> Advertising the option may lead to blindly copying of it without thinking
> about consequences. Recovering from such act may not be trivial.
> 
Agree.
> If one gets to this situation, he should change topology first. The error
> should suggest that.
I am OK for having suggestion related to changing such kind of topology rather than advertising about '--ignore-topology-disconnect' option

Martin/Abhijeet what is the current message?

Error messages are:   
"""
Replication topology in suffix '%(suffix)s' is disconnected:
%(errors)s""")

("""
Removal of '%(hostname)s' leads to disconnected topology in suffix '%(suffix)s':
%(errors)s""")


Which is clear enough. Closing per triage on Sep 27.

Right.