-
Bug
-
Resolution: Cannot Reproduce
-
Normal
-
odf-4.17
-
None
-
False
-
-
False
-
?
-
?
-
s390x
-
?
-
?
-
-
-
Moderate
-
None
Description of problem - Provide a detailed description of the issue encountered, including logs/command-output snippets and screenshots if the issue is observed in the UI:
After failover of the discovered application, the drpc is says failedover, but application still remains on primary cluster.
Affected application here is busybox-discovered
[root@a3e18015 ~]# oc get drpc busybox-discovered -n openshift-dr-ops
NAME AGE PREFERREDCLUSTER FAILOVERCLUSTER DESIREDSTATE CURRENTSTATE
busybox-discovered 168m m1320001 m1322001 Failover FailedOver
[root@a3e18015 ~]#
[root@a3e18015 ~]# oc get drpc busybox-discovered -n openshift-dr-ops -o jsonpath='{.status.progression}{"\n"}'
WaitForReadiness
[root@a3e18015 ~]#
[root@m1320001 ~]# oc -n busybox-discovered get pod,pvc
NAME READY STATUS RESTARTS AGE
pod/busybox-5968d74d47-zvjfl 1/1 Running 0 3h2mNAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS VOLUMEATTRIBUTESCLASS AGE
persistentvolumeclaim/busybox-pvc Bound pvc-608ff7e5-5952-4200-8eed-6965824c66da 1Gi RWO ocs-storagecluster-ceph-rbd <unset> 3h2m
[root@m1320001 ~]#
[root@m1320001 ~]# oc -n busybox-discovered get vr
NAME AGE VOLUMEREPLICATIONCLASS PVCNAME DESIREDSTATE CURRENTSTATE
busybox-pvc 35m rbd-volumereplicationclass-1625360775 busybox-pvc primary Primary
[root@m1320001 ~]#
[root@m1320001 ~]# oc get vrg -n openshift-dr-ops busybox-discovered
NAME DESIREDSTATE CURRENTSTATE
busybox-discovered primary Primary
[root@m1320001 ~]#
[root@m1322001 ~]# oc -n busybox-discovered get pod,pvc
No resources found in busybox-discovered namespace.
[root@m1322001 ~]#
[root@m1322001 ~]# oc -n busybox-discovered get vr
No resources found in busybox-discovered namespace.
[root@m1322001 ~]#
[root@m1322001 ~]# oc get vrg -n openshift-dr-ops busybox-discovered
NAME DESIREDSTATE CURRENTSTATE
busybox-discovered primary Unknown
[root@m1322001 ~]#
The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI):
IBMZ - zvm - UPI
The ODF deployment type (Internal, External, Internal-Attached (LSO), Multicluster, DR, Provider, etc):
DR
The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):
OCP : 4.17.3
ODF : 4.17.0-126
ACM : 2.12.0
Does this issue impact your ability to continue to work with the product?
yes.. Failover of discovered application does not work.
Is there any workaround available to the best of your knowledge?
Can this issue be reproduced? If so, please provide the hit rate
Yes
Can this issue be reproduced from the UI?
yes
If this is a regression, please provide more details to justify this:
Steps to Reproduce:
1.
2.
3.
The exact date and time when the issue was observed, including timezone details:
Actual results:
Expected results:
Logs collected and log location:
Additional info:
Must gather logs : https://drive.google.com/file/d/1v9hzz0KW1S5KRX-1emIBF2JsrirjB3VN/view?usp=sharing
This topic is being discussed in slack thread : https://ibm-systems-storage.slack.com/archives/C06GQDKEVGT/p1731071126037569
