Bug 2128142

Summary:	[MDR]VRG does not report DataReady if there are no PVCs protected in a MetroDR
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Amarnath <amk>
Component:	odf-dr	Assignee:	Shyamsundar <srangana>
odf-dr sub component:	ramen	QA Contact:	avdhoot <asagare>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	unspecified
Priority:	high	CC:	akrai, ebenahar, hnallurv, kseeger, mmuench, muagarwa, odf-bz-bot, rgowdege, rtalur, sheggodu, srangana
Version:	4.11
Target Milestone:	---
Target Release:	ODF 4.16.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.16.0-124	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-07-17 13:10:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Amarnath 2022-09-20 04:25:24 UTC

Description of problem (please be detailed as possible and provide log
snippets):

The relocation operation is not getting initiated.

Steps Followed:
Document followed : https://red-hat-storage.github.io/ocs-training/training/ocs4/odf411-metro-ramen.html#_create_data_policy_on_hub_cluster

1. Created Metro-DR setup.
2. After all validations created a Application.
3. Applied DR policy.
4. Application got deployed in preferred cluster ie., ocp-mr-2308-1
5. As Fencing was not applied, I tried Relocation operation to  ocp-mr-2308-2
by editing DRPC with action:Relocate and preferredCluster: ocp-mr-2308-2




Version of all relevant components (if applicable):
Build is OCP 4.11 + Odf 4.11 +ACM 2.5.1 +ceph 6.0

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?
No

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.
2.
3.


Actual results:


Expected results:


Additional info:

Comment 22 Karolin Seeger 2023-04-18 03:58:40 UTC

Moving out of 4.13 as per comment #21

Comment 36 akarsha 2024-01-24 04:36:08 UTC

*** Bug 2259203 has been marked as a duplicate of this bug. ***

Comment 44 avdhoot 2024-05-23 13:32:30 UTC


After discussion with dev I tried WA by creating drpc using cli but while doing relocation of app it stuck in initiating state 
due to Protected status is not true in drpc.

drpc status before initiating relocate-
========================================

status:
  actionDuration: 11.861792359s
  actionStartTime: "2024-05-23T12:37:43Z"
  conditions:
  - lastTransitionTime: "2024-05-23T12:37:27Z"
    message: Initial deployment completed
    observedGeneration: 1
    reason: Deployed
    status: "True"
    type: Available
  - lastTransitionTime: "2024-05-23T12:37:27Z"
    message: Ready
    observedGeneration: 1
    reason: Success
    status: "True"
    type: PeerReady
  - lastTransitionTime: "2024-05-23T12:37:27Z"
    message: VolumeReplicationGroup (helloword-ns/helloworldsub-placement-1-drpc)
      on cluster asagare-cl1 is not reporting any status about workload resources
      readiness, retrying till ClusterDataReady condition is met
    observedGeneration: 1
    reason: Unknown
    status: Unknown
    type: Protected
  lastUpdateTime: "2024-05-23T12:37:54Z"
  observedGeneration: 1
  phase: Deployed
  preferredDecision:
    clusterName: asagare-cl1
    clusterNamespace: asagare-cl1
  progression: Completed
  resourceConditions:
    resourceMeta:
      generation: 1
      kind: VolumeReplicationGroup
      name: helloworldsub-placement-1-drpc
      namespace: helloword-ns


drpc status after initiating relocate-
========================================

status:
  actionStartTime: "2024-05-23T12:55:07Z"
  conditions:
  - lastTransitionTime: "2024-05-23T12:55:07Z"
    message: current cluster (asagare-cl1) has not completed protection actions
    observedGeneration: 2
    reason: Initiating
    status: "False"
    type: Available
  - lastTransitionTime: "2024-05-23T12:37:27Z"
    message: Ready
    observedGeneration: 2
    reason: Success
    status: "True"
    type: PeerReady
  - lastTransitionTime: "2024-05-23T12:55:07Z"
    message: Missing VolumeReplicationGroup status from cluster asagare-cl2
    observedGeneration: 2
    reason: Unknown
    status: Unknown
    type: Protected
  lastUpdateTime: "2024-05-23T12:55:07Z"
  observedGeneration: 2
  phase: Initiating
  preferredDecision:
    clusterName: asagare-cl1
    clusterNamespace: asagare-cl1
  resourceConditions:
    resourceMeta:
      generation: 0
      kind: ""
      name: ""
      namespace: ""

Steps followed:
-----------------
1.Created app without pvc via UI
2.Created drpc using cli
3.tried to relocate via UI

Hence marking it as fail_QA.

Comment 45 Shyamsundar 2024-06-04 13:44:32 UTC

The root cause for the failure seems to be the same as https://bugzilla.redhat.com/show_bug.cgi?id=2283651 which is being fixed for 4.16.

I would suggest a retest using the CLI if possible post the above fix, to ensure that this use-case is also fixed. If not we can mark this for 4.17 and fix it correctly than depending on the Protected condition.

Comment 51 errata-xmlrpc 2024-07-17 13:10:29 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.16.0 security, enhancement & bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2024:4591