Symptoms
You see tests failing while waiting for pods to become Running. KuryrPort is created and populated with a VIF. In kuryr-cni logs you can see the pod actually got wired. In cri-o logs you can see the container got started. In kubelet logs you see lines like:

Error syncing pod, skipping" err="status.Image is not set" pod="default/kuryr-pod-90821034"

And similar ones related to status.Image not set.

Investigations
At this moment nobody knows why this is happening, but the node team suspects a cri-o issue. It's raised as https://github.com/cri-o/cri-o/issues/5709.