-
Bug
-
Resolution: Unresolved
-
Critical
-
odf-4.16
-
None
-
False
-
-
False
-
?
-
?
-
If docs needed, set a value
-
-
-
RamenDR sprint 2024 #18, RamenDR sprint 2024 #19
-
None
Description of problem (please be detailed as possible and provide log
snippests):
Version of all relevant components (if applicable):
OCP 4.16.0-0.nightly-2024-05-23-173505
ACM 2.11.0-DOWNSTREAM-2024-05-23-15-16-26
MCE 2.6.0-104
ODF 4.16.0-108.stable
Gitops v1.12.3
Platform- VMware
Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Is there any workaround available to the best of your knowledge?
Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
Can this issue reproducible?
Can this issue reproduce from the UI?
If this is a regression, please provide more details to justify this:
Steps to Reproduce:
1. On a RDR setup, when hub recovery is performed and we switch to the passive hub, we apply oc label namespace openshift-operators openshift.io/cluster-monitoring='true' label on this new hub to fire Vol.SyncDelay alert but WorkloadUnprotected is not being fired.
2.
3.
Actual results: [RDR] [Hub recovery] WorkloadUnprotected warning alert doesn't fire when switching hubs
Expected results: When hub is switched, WorkloadUnprotected should be fired on the new hub when a new workload is deployed or lastGroupSyncTime is reset on Failover operation when drpc Protected value is set to False.
Additional info: