Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1389183 - OCP 3.4 doesn't support to use RepoDigest for ImageID
OCP 3.4 doesn't support to use RepoDigest for ImageID
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod (Show other bugs)
3.4.0
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Solly Ross
Zhang Cheng
:
: 1392254 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-10-27 02:32 EDT by Zhang Cheng
Modified: 2017-03-08 13 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
The pod container status field ImageID was previously populated with a string of the form `docker://SOME_ID`. This displayed an image ID which was not usable to correlate the image running in the pod with an image stored on a registry. Now, the ImageID field is populated with a string of the form `docker-pullable://sha256@SOME_ID`. This image ID may be used to identify and pull the running image from the registry unambiguously.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-01-18 07:46:48 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:0066 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 12:23:26 EST

  None (edit)
Description Zhang Cheng 2016-10-27 02:32:47 EDT
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
Comment 1 Derek Carr 2016-10-27 15:35:36 EDT
This requires a fix to docker-1.10 that has not yet shipped in RHEL.  It's due Nov 5.
Comment 2 Derek Carr 2016-10-31 15:39:15 EDT
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.
Comment 3 Derek Carr 2016-11-01 10:23:42 EDT
origin pr:

https://github.com/openshift/origin/pull/11674
Comment 4 Troy Dawson 2016-11-04 14:59:59 EDT
This has been merged into ose and is in OSE v3.4.0.22 or newer.
Comment 6 Solly Ross 2016-11-04 16:18:33 EDT
I noticed an issue and posted a second PR: https://github.com/openshift/origin/pull/11793
Comment 7 DeShuai Ma 2016-11-06 20:42:44 EST
wait PR 11793 merge
Comment 8 Andy Goldstein 2016-11-07 15:18:58 EST
In the merge queue
Comment 9 Seth Jennings 2016-11-08 13:35:05 EST
*** Bug 1392254 has been marked as a duplicate of this bug. ***
Comment 10 Troy Dawson 2016-11-09 14:51:59 EST
This has been merged into ose and is in OSE v3.4.0.24 or newer.
Comment 11 Zhang Cheng 2016-11-14 00:57:59 EST
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
Comment 13 errata-xmlrpc 2017-01-18 07:46:48 EST
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

Note You need to log in before you can comment on or make changes to this bug.