1. Create pod with YAML in comment 0
2. Wait until pods becomes ImagePullBackOff status in CLI
# oc get pods -n yapei44
NAME   READY   STATUS             RESTARTS   AGE
test   1/2     ImagePullBackOff   0          24s
# oc describe pod test -n yapei44
Containers:
  container1:
    Container ID:  
    Image:         busybox_error
    Image ID:      
    Port:          <none>
    Host Port:     <none>
    Command:
      sleep
      1
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-92t6j (ro)
  container2:
    Container ID:  cri-o://4df9802f5e3a3f56a760362273b66e636976db8569c86cabe71b0bfaf4eaaf83
    Image:         busybox
    Image ID:      docker.io/library/busybox@sha256:a2490cec4484ee6c1068ba3a05f89934010c85242f736280b35343483b2264b6
    Port:          <none>
    Host Port:     <none>
    Command:
      sleep
      100
    State:          Running
      Started:      Thu, 16 Apr 2020 23:21:36 -0400
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-92t6j (ro)
3. Check pod status on console, it shows 'ImagePullBackOff' on Pod list page and Pod details page

Verified on     4.4.0-0.nightly-2020-04-16-231032

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, 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-2020:0581