Created attachment 1677189 [details] Dropdown Description of problem: Users are unable to deploy images from "openshift" namespace in the UI but they can do it using the CLI. Version-Release number of selected component (if applicable): 4.3.8 How reproducible: Always Steps to Reproduce: 1. Log in console and open the developer perspective 2. Click on "+ Add" and then choose "Container Image" 3. Choose "Image name from internal registry" and expand the dropdown Actual results: There's no "openshift" namespace. See attachment #1 [details]. Expected results: See the "openshift" namespace and deploy any image from it Additional info: The "openshift" has been always there to provide templates and images. Actually the images can be used from the CLI, so there's nothing to be fixed in the permissions (users are already capable of read is and istag resources in the namespace): [sgarciam@localhost ~]$ oc whoami sgarcia [sgarciam@localhost ~]$ oc auth can-i get istag -n openshift yes [sgarciam@localhost ~]$ oc auth can-i get is -n openshift yes [sgarciam@localhost ~]$ oc new-app redis:3.2 --> Found image a00c397 (6 months old) in image stream "openshift/redis" under tag "3.2" for "redis:3.2" ...
In the Deploy Image form, we list all projects a user has access to followed by a drop down for the image streams the user can list in that project. A self provisioner cannot list the openshift namespace but they can list imagestreams in that namespace. Therefore the user never sees the openshift namespace as an option. In 3.11 we included the openshift namespace in this list. We should do the same.
Created attachment 1685598 [details] Openshift is there in the drop down menu
I have validated the bugzilla on: Build:4.5.0-0.ci-2020-05-05-224426 Browser:Google Chrome Version 81.0.4044.129 Please have a look at the screenshot attached Marking this as verified.
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-2020:2409