Cause: Users with limited permissions is not able to pull the clusterwide imagestreams
Consequence: In deploy image, Internal registry imagestreams are not shown even if there is some imagestream in the namespace.
Fix: Moved the imagestream fetching logic from cluster level to namespace level
Result: If the user has permisssion to few namespaces, then all the imagestreams in those namespaces will be shown to the user.
Description of problem:
No imagestreams detected when Deploy Image with "Image name from internal registry" from webconsole
Version-Release number of selected component (if applicable):
4.4.0-0.ci-2019-12-14-210519
How reproducible:
always
Steps to Reproduce:
1.Login to webconsole with common user,and create a project
2.Create or generate an imagestream under project
$oc new-build ruby~https://github.com/openshift/ruby-hello-world.git
$oc get is
ruby-hello-world image-registry.openshift-image-registry.svc:5000/wxj/ruby-hello-world latest 12 minutes ago
3.Deploy image via click "Container image" catalog, then choose "Image name from internal registry"
Actual results:
Step 3: No imagestreams detected under project when an imagestream exists.
Expected results:
Could detecte the existing imagestream.
Additional info:
Test this issue with 4.4.0-0.nightly-2020-01-08-194939, and fixed.
Could detect the imagestream and tag under project from `Image name from internal registry`
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:0581