cri-o: Fails to pull image if it already exists with different schema version

Description

While running sonobuoy conformance tests I noticed image pull failures:

Failed to pull image "k8s.gcr.io/pause:3.1": rpc error: code = Unknown desc = Error committing the finished image: image with ID "da86e6ba6ca197bf6bc5e9d900febd906b133eaa4750e6bed647b0fbe50ed43e" already exists, but uses a different top layer: that ID is already in use

Most likely this happens because my setup has the same pause image with a different name.

Steps to reproduce the issue:

1. setup kubernetes with a custom pause image (that is exactly the same as “k8s.gcr.io/pause:3.1”)
2. run sonobuoy
3. pods with “k8s.gcr.io/pause:3.1” fail

Describe the results you received:

cri-o fails to pull image.

Describe the results you expected:

image pull succeeds.

Output of crio --version:

crio version 1.11.1
commit: ""

Additional environment details (AWS, VirtualBox, physical, etc.):

• Kubernetes 1.11.1 (Kontena Pharos v1.3.0-beta.1 , https://github.com/kontena/pharos-cluster/releases/tag/v1.3.0-beta.1)
• CentOS 7.5
• DigitalOcean