Bug 2079866

Summary: [DR] odf-multicluster-console is in CLBO state
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Pratik Surve <prsurve>
Component: odf-drAssignee: gowtham <gshanmug>
odf-dr sub component: multicluster-orchestrator QA Contact: kmanohar
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: unspecified CC: ebenahar, gshanmug, jefbrown, kramdoss, madam, muagarwa, nthomas, ocs-bugs, odf-bz-bot
Version: 4.11Keywords: TestBlocker
Target Milestone: ---   
Target Release: ODF 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.11.0-66 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-24 13:51:03 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-04-28 12:04:57 UTC 
Description of problem (please be detailed as possible and provide log
snippets):

[DR] odf-multicluster-console is in CLBO state

Version of all relevant components (if applicable):
OCP version:- 4.11.0-0.nightly-2022-04-26-181148
ODF version: 4.11.0-56
ACM version:- 2.5

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. Install MCO operator
3. Check Pod status inside openshift-operators namespace


Actual results:
# oc get pods
NAME                                        READY   STATUS             RESTARTS      AGE
odf-multicluster-console-bb8866774-fhscb    0/1     CrashLoopBackOff   6 (52s ago)   7m6s
odfmo-controller-manager-7cf7bb5b5d-zctp2   1/1     Running            0             7m6s
ramen-hub-operator-64767db4c6-mnnzh         2/2     Running            0             7m4s


# oc logs odf-multicluster-console-bb8866774-fhscb -p                                        
/usr/bin/container-entrypoint: line 2: exec: --: invalid option
exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]


oc describe po odf-multicluster-console-bb8866774-fhscb -> http://pastebin.test.redhat.com/1048268

Expected results:
Pod should be in Running state


Additional info:
Comment 6 kmanohar 2022-07-22 05:39:54 UTC 
VERIFICATION COMMENTS:-

Verified build - 4.11-113

oc get pods
NAME                                        READY   STATUS    RESTARTS   AGE
odf-multicluster-console-6b7bf84d79-b7ppw   1/1     Running   0          2d23h
odfmo-controller-manager-77c749d44-bm5w6    1/1     Running   0          2d23h
ramen-hub-operator-84f8d7d46c-88wvc         2/2     Running   0          2d23h
Comment 7 kmanohar 2022-07-22 05:44:32 UTC 
VERIFICATION COMMENTS

oc describe pod odf-multicluster-console-6b7bf84d79-b7ppw - http://pastebin.test.redhat.com/1066879
Comment 9 errata-xmlrpc 2022-08-24 13:51:03 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