Red Hat Bugzilla – Bug 1609204
[admin] Pod selector link should not point to "all projects" searching page.
Last modified: 2018-10-11 03:22:46 EDT
Description of problem: Common user creates dc in project, then click link under "POD SELECTOR" on dc overview page, it jumps to all project searching page, on which user has no permission to list pod. Version-Release number of selected component (if applicable): openshift v3.11.0-0.9.0 kubernetes v1.11.0+d4cacc0 registry.reg-aws.openshift.com:443/openshift3/ose-console v3.11 e03103f86278 3 days ago 273 MB How reproducible: Always Steps to Reproduce: 1.Create dc in project. # oc run testdc --image=aosqe/hello-openshift -n protest 2.On console, goto the "testdc" page, on "Overview' tab, click link under "POD SELECTOR". 3. Actual results: 2.It jumps to all project searching page, and user has no permission to list pods. The link url is "https://console.****/search/all-namespaces?kind=Pod&q=run%3Dtestdc" Expected results: 2.Should jump to current project searching page. Additional info: Same issue exists for other resources' "POD SELECTOR" link, eg, deployment, service,rc, statefulset and so on.
https://github.com/openshift/console/pull/324
Kubernetes v1.11.0+d4cacc0 OpenShift v3.11.0-0.10.0 ose-console v3.11 abfda950c7e7 8 hours ago 273 MB Tested on ocp 3.11 with above version, all "POD SELECTOR' link will open searching page for current project, and the search result is correct. The bug has been fixed, so move it to Verified.
Pod Selector also need to be fixed on Resources list page: Deployment Configs Deployments Replication Controllers Replica Sets Daemon Sets
https://github.com/openshift/console/pull/407
Pod selector link on services list page still points to "all project" search page.
Follow on fix for services: https://github.com/openshift/console/pull/455
openshift v3.11.0-0.24.0 kubernetes v1.11.0+d4cacc0 registry.dev.redhat.io/openshift3/ose-console v3.11.0 e174a3b28f9ab 283MB Checked on OCP env with above version, the issue in Comment 6 has been fixed. The bug has been fixed, so move it to 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-2018:2652