Bug 2273533 - [RDR] Unexpected webhook MCO error when creating additional DRPolicy from the ACM console
Summary: [RDR] Unexpected webhook MCO error when creating additional DRPolicy from the...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-dr
Version: 4.15
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ODF 4.16.0
Assignee: Vineet
QA Contact: kmanohar
URL:
Whiteboard:
Depends On:
Blocks: 2276664
TreeView+ depends on / blocked
 
Reported: 2024-04-04 21:08 UTC by Annette Clewett
Modified: 2024-07-17 13:18 UTC (History)
4 users (show)

Fixed In Version: 4.16.0-89
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2276664 (view as bug list)
Environment:
Last Closed: 2024-07-17 13:18:06 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github red-hat-storage odf-multicluster-orchestrator pull 203 0 None Merged Bug 2273533: Return not found error 2024-04-24 08:47:47 UTC
Red Hat Product Errata RHSA-2024:4591 0 None None None 2024-07-17 13:18:08 UTC

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


Note You need to log in before you can comment on or make changes to this bug.