Bug 1375145

Summary: istag displays "Unknown Layer" and lost image id which size is 0
Product: OpenShift Container Platform Reporter: XiaochuanWang <xiaocwan>
Component: Management ConsoleAssignee: Martin Pitt <mpitt>
Status: CLOSED WONTFIX QA Contact: XiaochuanWang <xiaocwan>
Severity: low Docs Contact:
Priority: medium    
Version: 3.3.0CC: aos-bugs, jforrest, jokerman, mmccomas, spadgett, xiaocwan, yapei
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-06-04 20:39:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
istag display Unknown_Layer
none
unknow layer on OCP 3.5 and OCP 4.6 none

Description XiaochuanWang 2016-09-12 09:45:36 UTC 
Created attachment 1200137 [details]
istag display Unknown_Layer

Description of problem:
After create a is contains image layer with size 0, the istag page displays "Unknown Layer", also there's no image id.

Version-Release number of selected component (if applicable):
oc/openshift 3.3.0.30

How reproducible:
Always

Steps to Reproduce:
1. oc new-app https://raw.githubusercontent.com/openshift/origin/master/examples/sample-app/application-template-stibuild.json
2. check is tag by `oc get istag <is:tag> -o yaml`
3. Go to Builds->Images page, check Layers when there are 0 sized images 

Actual results:
Layers of istag displays "Unknown Layer", also there's no image id.

Expected results:
The image which size is 0 should display the image id and the size on the right place

Additional info:
Please refer to the screenshot.
Comment 1 Jessica Forrester 2016-12-07 21:57:47 UTC 
@dominik or @stef can you guys look into this?
Comment 2 Jessica Forrester 2017-01-16 15:45:34 UTC 
@dominik this one affects the openshift console and not just the registry which is why it wasn't tagged as [atomic registry] we need to make sure this one continues to get tracked as an OCP bug
Comment 3 Yadan Pei 2017-02-14 06:30:35 UTC 
Removed the [atomic registry] as Jessica said in comment 2
Comment 4 Peter 2017-05-06 00:54:07 UTC 
Tested with

openshift v1.5.0+031cbe4
kubernetes v1.5.2+43a9be4

And could not reproduce. Are you still able to reproduce?
Comment 5 XiaochuanWang 2017-05-11 12:54:28 UTC 
OCP 3.5 does not reproduced, will check on latest OCP 3.6 again
OpenShift Master:     v3.5.5.13
Kubernetes Master:    v1.5.2+43a9be4
Comment 6 XiaochuanWang 2017-05-11 13:04:23 UTC 
Sorry, please ignore the last comment, it does reproduce on OCP 3.5 and OCP 3.6.
Please see the attachment "unknown_layer.png"

User with view permission for project "openshift" could see the unknow layers of image tag
Browse to https://xxx:8443/console/project/openshift/browse/images/mongodb/2.4?tab=meta

Tested on:
OpenShift Master:     v3.5.5.13
Kubernetes Master:    v1.5.2+43a9be4

OpenShift Master:     v3.6.74
Kubernetes Master:    v1.6.1+5115d708d7
Comment 7 XiaochuanWang 2017-05-11 13:04:57 UTC 
Created attachment 1277885 [details]
unknow layer on OCP 3.5 and OCP 4.6
Comment 8 Peter 2017-05-11 13:26:42 UTC 
Where did the mongo image come from. I don't see it referenced in the example yaml above. Want to make sure i'm using the same image.
Comment 9 XiaochuanWang 2017-05-12 01:50:08 UTC 
As Comment 6 metioned, User with view permission of the project "openshift" could see the imagestreams. Because for OCP env, by default the imagestreams are created in project "openshift".

You can also create them in your project by https://raw.githubusercontent.com/openshift/origin/master/examples/image-streams/image-streams-rhel7.json
Comment 11 Samuel Padgett 2019-06-04 20:39:53 UTC 
This bug does not apply to the new 4.1 console. We do not plan to address this in the 3.x console.