Bug 2273533

Summary: [RDR] Unexpected webhook MCO error when creating additional DRPolicy from the ACM console
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Annette Clewett <aclewett>
Component: odf-drAssignee: Vineet <vbadrina>
odf-dr sub component: multicluster-orchestrator QA Contact: kmanohar
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: amagrawa, kseeger, muagarwa, vbadrina
Version: 4.15   
Target Milestone: ---   
Target Release: ODF 4.16.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.16.0-89 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 2276664 (view as bug list) Environment:
Last Closed: 2024-07-17 13:18:06 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: 2276664    

Description Annette Clewett 2024-04-04 21:08:09 UTC
Created attachment 2025300 [details]
Graphic for webhook UI error

Description of problem (please be detailed as possible and provide log
snippests):
Created RDR test environment with 5 OCP clusters. Cluster hyper2 is the hub with ACM and 2 sets of managed clusters; hyper3<->hyper4 and hyper5<->hyper6. All 4 clusters had ODF 4.15 installed. 

After getting clusters imported into ACM and configuring Submariner between the peer clusters MCO was installed and the first DRPolicy created between hyper3<->hyper4. I validated that mirroring was enabled, object buckets created, DR cluster operators installed, and secrets exchanged. 

I then attempted to create a 2nd DRPolicy for hyper5<->hyper6. This fails with a webhook error (graphic attached). The only resource created was the new DRPolicy on the hub (hyper2) cluster.

Version of all relevant components (if applicable):
OCP 4.15.3
ODF 4.15.0
ACM 2.10.0
Submariner 0.17

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
Yes, DR is not configured for 2nd set of Peer clusters

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)?
4

Can this issue reproducible?
Only tested one time

Can this issue reproduce from the UI?
Yes

Steps to Reproduce:
1. Create RDR config with hub + 4 managed clusters (2 Peer clusters)
2. Create DRPolicy for first Peer Cluster and validate
3. Create DRPolicy for second Peer Cluster


Actual results:
There is UI error in Create DRPolicy and only drpolicy is created

Expected results:
There is no UI error and DR configuration is created exactly the same as first Peer Cluster for second set of cluster (2nd Peer Cluster).

Comment 13 Vineet 2024-05-31 06:02:21 UTC
No

Comment 15 errata-xmlrpc 2024-07-17 13:18:06 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