Description of problem: In Web Console, in the image section (Builds -> Image -> <image_name> -> latest -> Identifier) there is section 'Identifier" which is sometimes null or hash other than image digest hash. Screenshot attached. What the identifier is and for what it is used? Version-Release number of selected component (if applicable): OpenShift Container Platform How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
(In reply to Vladislav Walek from comment #0) > Description of problem: > > In Web Console, in the image section (Builds -> Image -> <image_name> -> > latest -> Identifier) there is section 'Identifier" which is sometimes null > or hash other than image digest hash. > > Screenshot attached. What the identifier is and for what it is used? This was valid for the v1 images where this identifier mapped to Image field[1]. However, for v2 images we don't set this and in the latest version we don't store the manifest at all, thus this field should be removed from the web console. Jessica, Jakub told me that we still have this field there, mind taking this bug and nuking it? [1] https://github.com/mfojtik/origin/blob/master/pkg/image/api/dockerpre012/dockertypes.go#L45
Hello Michal, thank you for reply. In which version it will be removed? Thx
This part of the UI is owned by the cockpit team / registry UI team. Michal what else are we losing from the ImageStreamImage that we were displaying in the console? When you say we aren't storing the manifest anymore, what all does that include?
Submitted PR for fixing this bug: https://github.com/openshift/registry-image-widgets/pull/6
Verified in env: openshift v3.6.0-alpha.1+2aff95e-12 kubernetes v1.5.2+43a9be4 etcd 3.1.0 identifier is disappears.
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/RHSA-2017:3188