Bug 2085351

Summary:	[DR] Mirrorpeer failed to create with msg Internal error occurred
Product:	[Red Hat Storage] Red Hat OpenShift Data Foundation	Reporter:	Pratik Surve <prsurve>
Component:	odf-dr	Assignee:	Vineet <vbadrina>
odf-dr sub component:	multicluster-orchestrator	QA Contact:	kmanohar
Status:	CLOSED ERRATA	Docs Contact:
Severity:	urgent
Priority:	unspecified	CC:	amagrawa, ekuric, kramdoss, madam, mmuench, muagarwa, ocs-bugs, odf-bz-bot
Version:	4.11
Target Milestone:	---
Target Release:	ODF 4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.11.0-89	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-24 13:52:56 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 Pratik Surve 2022-05-13 05:14:41 UTC

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

[DR] Mirrorpeer failed to create with msg Internal error occurred: failed calling webhook "vmirrorpeer.kb.io": failed to call webhook: Post "https://odfmo-controller-manager-service.openshift-operators.svc:443/validate-multicluster-odf-openshift-io-v1alph


Version of all relevant components (if applicable):
OCP version:- 4.11.0-0.nightly-2022-05-11-054135
ACM version:- 2.5
ODF version:- 4.11.0-69

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?


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 DR cluster 
2. Deploy MCO operator
3. Create a mirror peer and you will see the issue


Actual results:
Error from server (InternalError): error when creating "mirrorpeer.yaml.new": Internal error occurred: failed calling webhook "vmirrorpeer.kb.io": failed to call webhook: Post "https://odfmo-controller-manager-service.openshift-operators.svc:443/validate-multicluster-odf-openshift-io-v1alpha1-mirrorpeer?timeout=10s": dial tcp 10.129.2.17:9443: connect: connection refused


Expected results:
Mirrorpeer creation should work

Additional info:

Csv:-http://pastebin.test.redhat.com/1051578 
(Note) as a workaround i have set failurePolicy to Ignore

Comment 3 gowtham 2022-05-18 03:31:39 UTC

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

Comment 7 kmanohar 2022-07-21 08:03:26 UTC

VERIFICATION COMMENTS

verified build - 4.11-113

mirrorpeer status

apiVersion: multicluster.odf.openshift.io/v1alpha1
kind: MirrorPeer
metadata:
  creationTimestamp: "2022-07-18T08:31:26Z"
  finalizers:
  - hub.mirrorpeer.multicluster.odf.openshift.io
  - kmanohar-clu2.spoke.mirrorpeer.multicluster.odf.openshift.io
  - kmanohar-clu1.spoke.mirrorpeer.multicluster.odf.openshift.io
  generateName: mirror-peer-
  generation: 1
  labels:
    cluster.open-cluster-management.io/backup: resource
  name: mirror-peer-747hq
  resourceVersion: "1871824"
  uid: e0890898-314f-477e-852a-ce69d796ed9c
spec:
  items:
  - clusterName: kmanohar-clu1
    storageClusterRef:
      name: ocs-storagecluster
      namespace: openshift-storage
  - clusterName: kmanohar-clu2
    storageClusterRef:
      name: ocs-storagecluster
      namespace: openshift-storage
  manageS3: true
  schedulingIntervals:
  - 5m
  type: async
status:
  phase: ExchangedSecret

Comment 9 errata-xmlrpc 2022-08-24 13:52:56 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.11.0 security, enhancement, & bugfix 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-2022:6156