% oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.0-0.nightly-2022-08-03-161023 True False 46m Cluster version is 4.10.0-0.nightly-2022-08-03-161023 % oc get nodes NAME STATUS ROLES AGE VERSION ip-10-0-134-29.us-east-2.compute.internal Ready master 63m v1.23.5+012e945 ip-10-0-136-5.us-east-2.compute.internal Ready worker 59m v1.23.5+012e945 ip-10-0-170-12.us-east-2.compute.internal Ready master 64m v1.23.5+012e945 ip-10-0-176-11.us-east-2.compute.internal Ready worker 57m v1.23.5+012e945 ip-10-0-194-176.us-east-2.compute.internal Ready worker 59m v1.23.5+012e945 ip-10-0-194-203.us-east-2.compute.internal Ready master 64m v1.23.5+012e945 % cat podp.yaml apiVersion: v1 kind: Pod metadata: name: proapagate-pod spec: volumes: - name: host hostPath: path: / containers: - name: propagate-pod image: nginx securityContext: privileged: true volumeMounts: - name: host mountPath: /host mountPropagation: HostToContainer % oc apply -f podp.yaml pod/proapagate-pod created % oc get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES proapagate-pod 1/1 Running 0 11s 10.129.2.8 ip-10-0-176-11.us-east-2.compute.internal <none> <none> % oc debug node/ip-10-0-176-11.us-east-2.compute.internal Starting pod/ip-10-0-176-11us-east-2computeinternal-debug ... ... sh-4.4# crictl ps | grep propa 2ae3603758cb0 docker.io/library/nginx@sha256:ecc068890de55a75f1a32cc8063e79f90f0b043d70c5fcf28f1713395a4b3d49 48 seconds ago Running propagate-pod 0 7865822714e49 sh-4.4# crictl inspect 2ae3603758cb0 | grep -A 5 -B 5 PROPAGATION_HOST_TO_CONTAINER }, "mounts": [ { "containerPath": "/host", "hostPath": "/", "propagation": "PROPAGATION_HOST_TO_CONTAINER", "readonly": false, "selinuxRelabel": false }, { "containerPath": "/etc/hosts",
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.10.28 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:6095