Bug 2218181

Summary: [IBM Z/MDR]: With ACM 2.8 applying DRpolicy to subscription workload fails
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Sravika <sbalusu>
Component: odf-drAssignee: rakesh-gm <rgowdege>
odf-dr sub component: ramen QA Contact: Parikshith <pbyregow>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: hnallurv, kseeger, muagarwa, ocs-bugs, odf-bz-bot, rgowdege, srangana
Version: 4.13Keywords: Regression
Target Milestone: ---   
Target Release: ODF 4.13.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.13.1-3 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2219797 (view as bug list) Environment:
Last Closed: 2023-08-02 16:07:42 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:
Bug Depends On:    
Bug Blocks: 2219797    

Description Sravika 2023-06-28 11:30:46 UTC
Created attachment 1972999 [details]
ramen-hub-operator.log

Description of problem (please be detailed as possible and provide log
snippests):
[IBM Z/MDR]: With ACM 2.8 applying DRpolicy to subscription workload fails

Version of all relevant components (if applicable):
OCP version:- 4.13.0
ODF version:- 4.13.0-218
ACM version:- 2.8

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes

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

Can this issue reproduce from the UI?


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Deploy MDR environment
2. Create subscription based application from hub cluster
3. Apply DR policy to the application 
4. When the Apply DRPolicy modal is displayed, select the application and enter PVC label as appname=""

Actual results:
Failed to deploy DRPC and the drpc status on the hub cluster is not Deployed state


2023-06-28T11:10:11.589Z        ERROR   controller/controller.go:329    Reconciler error        {"controller": "drplacementcontrol", "controllerGroup": "ramendr.openshift.io", "controllerKind": "DRPlacementControl", "DRPlacementControl": {"name":"busybox-placement-1-drpc","namespace":"busybox-sample"}, "namespace": "busybox-sample", "name": "busybox-placement-1-drpc", "reconcileID": "9dc4b924-bf27-4df9-a999-0ada10d51efc", "error": "failed to create DRPC instance (ApplicationSet list: no matches for kind \"ApplicationSet\" in version \"argoproj.io/v1alpha1\") and (<nil>)"}
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
        /remote-source/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime.5/pkg/internal/controller/controller.go:329
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
        /remote-source/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime.5/pkg/internal/controller/controller.go:274
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
        /remote-source/deps/gomod/pkg/mod/sigs.k8s.io/controller-runtime.5/pkg/internal/controller/controller.go:235



Expected results:

DRPC should be in Deployed state

Additional info:

Must-gather logs:
https://drive.google.com/file/d/1IpiP2Wj4YOpObjxqL2_IT8xdA_0wmSCI/view?usp=sharing

Comment 13 Sravika 2023-07-19 07:17:13 UTC
Verified this fix on IBM Z on ACM 2.8 and ODF/MCO version: 4.13.1-8 and it works fine

Comment 19 errata-xmlrpc 2023-08-02 16:07:42 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 (Moderate: Red Hat OpenShift Data Foundation 4.13.1 security and 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-2023:4437