Verified on 4.8.0-0.nightly-2022-05-26-033316 % oc get pod NAME READY STATUS RESTARTS AGE demo-pod 0/1 CreateContainerError 0 6m29s sh-4.4# find /var/log/pods/ -type f | grep demo sh-4.4# when ContainerCreateError loop, not generate any empty logfiles.
Please ignore comment 6 % oc get pod NAME READY STATUS RESTARTS AGE demo-pod 0/1 CreateContainerError 0 7m49s sh-4.4# find /var/log/pods/ -type f | grep demo sh-4.4# sh-4.4# sh-4.4# when ContainerCreateError loop, not generate any empty logfiles. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.9.0-0.nightly-2022-05-26-083338 True False 127m Cluster version is 4.9.0-0.nightly-2022-05-26-083338
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 (OpenShift Container Platform 4.9.36 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/RHBA-2022:4741