Created attachment 1849806 [details] hyperconverged-cluster-cli-download-7697598548-s9gft.yaml Description of problem: When trying to deploy RHEL9 based CNV-4.10.0 hyperconverged-cluster-cli-download pod can't start. [cnv-qe-jenkins@c01-verify-410-298nj-executor ~]$ oc get pods NAME READY STATUS RESTARTS AGE cdi-operator-7b9477c8d8-pkjgg 1/1 Running 0 38m cluster-network-addons-operator-696947bc4-z9bxp 1/1 Running 0 38m hco-operator-67bb865f6f-hdhnn 1/1 Running 0 38m hco-webhook-84c5fc7df9-4bgb9 1/1 Running 0 38m hostpath-provisioner-operator-86cf85b6fc-m8b7p 1/1 Running 0 38m hyperconverged-cluster-cli-download-7697598548-s9gft 0/1 CrashLoopBackOff 12 (100s ago) 38m node-maintenance-operator-controller-manager-f8d99b596-wrjcx 1/1 Running 0 38m ssp-operator-6bbd4c9749-kk5g5 1/1 Running 0 38m virt-operator-89c9dcdb5-dcb4f 1/1 Running 0 38m virt-operator-89c9dcdb5-r9s4h 1/1 Running 0 38m [cnv-qe-jenkins@c01-verify-410-298nj-executor ~]$ oc logs hyperconverged-cluster-cli-download-7697598548-s9gft nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied) 2022/01/10 07:46:43 [emerg] 1#1: open() "/var/log/nginx/error.log" failed (13: Permission denied) Version-Release number of selected component (if applicable): HCO-v4.10.0.rhel9-4. How reproducible: 100 Steps to Reproduce: 1. Deploy RHEL9 based CNV-4.10.0. 2. 3. Actual results: Pod stuck on CrashLoopBackOff. Expected results: Pod to start. Additional info: Attached pod logs.
hco-bundle-registry-container-v4.10.0.rhel9-6 is finally green in CVP, moving to ON_QA
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 (Moderate: OpenShift Virtualization 4.10.1 Images security and 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-2022:4668