Hide Forgot
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.
@dominik or @stef can you guys look into this?
@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
Removed the [atomic registry] as Jessica said in comment 2
Tested with openshift v1.5.0+031cbe4 kubernetes v1.5.2+43a9be4 And could not reproduce. Are you still able to reproduce?
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
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
Created attachment 1277885 [details] unknow layer on OCP 3.5 and OCP 4.6
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.
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
This bug does not apply to the new 4.1 console. We do not plan to address this in the 3.x console.