Description of problem: The code of user story "[node] Pod.Status.ContainerStatuses.ImageID value needs to match image digest for trackability" had been merged in OCP3.3.1, but not exist in OCP3.4 Version-Release number of selected component (if applicable): # openshift version openshift v3.4.0.16+cc70b72 kubernetes v1.4.0+776c994 etcd 3.1.0-rc.0 # docker version 1.12.1 How reproducible: Always Steps to Reproduce: 1. oc create -f pod-pull-by-digests.yaml apiVersion: v1 kind: Pod metadata: name: pod-pull-by-digests labels: app: pod-pull-by-digests spec: containers: - name: hello-pod image: docker.io/deshuai/hello-pod@sha256:90b815d55c95fffafd7b68a997787d0b939cdae1bca785c6f52b5d3ffa70714f ports: - containerPort: 80 2. check image info from pod status oc get pod pod-pull-by-digests -o yaml Actual results: imageID: docker://sha256:e6a47a29d0e2749c873134622635a69badbedc98ea23791a2b152663d797c4dc Expected results: Should be: imageID: docker-pullable://docker.io/deshuai/hello-pod@sha256:90b815d55c95fffafd7b68a997787d0b939cdae1bca785c6f52b5d3ffa70714f addition info: None
This requires a fix to docker-1.10 that has not yet shipped in RHEL. It's due Nov 5.
Actually, to clarify, the test would be against docker 1.12. Solly - please confirm you actually cherry-picked this to openshift/origin:master. I suspect we need to pick it.
origin pr: https://github.com/openshift/origin/pull/11674
This has been merged into ose and is in OSE v3.4.0.22 or newer.
I noticed an issue and posted a second PR: https://github.com/openshift/origin/pull/11793
wait PR 11793 merge
In the merge queue
*** Bug 1392254 has been marked as a duplicate of this bug. ***
This has been merged into ose and is in OSE v3.4.0.24 or newer.
Verified and Passed. Code have been merged in 3.4 latest version. Test Env: oc v3.4.0.25+1f36858 kubernetes v1.4.0+776c994
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-2017:0066