ClusterLabs / ClusterLabs/anvil
[DR] anvil-manage-dr --dr-host $(hostname) --unlink --anvil an-anvil-01 causes havoc if resources are still configured
- Dominant language
- Perl
- Stars
- 7
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
the first impact is that DR goes to down the drain badly and there is no apparent way to recover it.
First of all, design decision here. How should "--unlink" behave when resources are configured?
1) fail to unlink, list of resources (such as protected servers and linked storage groups) should be presented to the enduser
2) automatically delete all related resources and then unlink.
IMHO 1 is perfectly acceptable, but 2 is also ok with extra coding.
unlink the DR partially stops / deconfigure replication, but doesn´t delete resources that are left there hanging in a limbo, like DRBD drops connections, but nothing delete the resources.
Unclear if it´s a design problem or a bug.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.