fix show success decorator for FailedOver on DR topology#2800
Conversation
getDecoratorForStatus mapped DRStatus.FailedOver to the warning triangle while sidebar-utils and disaster-recovery already treat FailedOver as a successful completed failover. Topology app nodes use getDecoratorForStatus for quadrant decorators, which caused the BZ mismatch on the target cluster. Align FailedOver with Relocated/Healthy: CheckCircle and NodeStatus.success. Signed-off-by: Timothy Asir Jeyasingh <tim.gluster@gmail.com>
|
before: after: |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: SanjalKatiyar, TimothyAsirJeyasing The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/cherry-pick release-4.22 |
|
@SanjalKatiyar: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
3 participants
https://redhat.atlassian.net/browse/DFBUGS-6797
getDecoratorForStatus mapped DRStatus.FailedOver to the warning triangle while sidebar-utils and disaster-recovery already treat FailedOver as a successful completed failover. Topology app nodes use getDecoratorForStatus for quadrant decorators, which caused the BZ mismatch on the target cluster.
Align FailedOver with Relocated/Healthy: CheckCircle and NodeStatus.success.