Description of problem (please be detailed as possible and provide log snippests): [RDR] odf-multicluster-console is in CLBO oc logs odf-multicluster-console-5869ff58cb-nbkfs ln: failed to create symbolic link '/var/log/nginx/access.log': Permission denied Version of all relevant components (if applicable): OCP version:- 4.14.0-0.nightly-2023-10-16-104540 ODF version:- 4.14.0-152 ACM version:- 2.9.0-185 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? 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)? 1 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 MCO operator 2. check pod status in openshift-operator namespace 3. Actual results: oc logs odf-multicluster-console-5869ff58cb-nbkfs ln: failed to create symbolic link '/var/log/nginx/access.log': Permission denied $pods NAME READY STATUS RESTARTS AGE odf-multicluster-console-5869ff58cb-nbkfs 0/1 CrashLoopBackOff 6 (82s ago) 7m14s odfmo-controller-manager-7776db8c4c-jczv6 1/1 Running 0 7m14s ramen-hub-operator-7d66667f8c-zwvvg 2/2 Running 0 10m Expected results: pod should not be in CLBO state Additional info:
Verified in version: $ oc get csv odf-multicluster-orchestrator.v4.14.0-rhodf -o yaml | grep full_version full_version: 4.14.0-156 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.14.0-0.nightly-2023-10-18-004928 True False 4d23h Cluster version is 4.14.0-0.nightly-2023-10-18-004928 The pod "odf-multicluster-console" is in Running state. $ oc get pods -n openshift-operators NAME READY STATUS RESTARTS AGE odf-multicluster-console-d599b6f6f-zbqc9 1/1 Running 0 2d13h odfmo-controller-manager-6b447ffddb-2ms9p 1/1 Running 0 16h ramen-hub-operator-58b758646b-jfjd9 2/2 Running 0 2d13h Verification is done in RDR setup.
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.14.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-2023:6832