Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1784352

Summary:	User can list pods, but not allowed to list the deployment pods or replica set pods
Product:	OpenShift Container Platform	Reporter:	Udi Kalifon <ukalifon>
Component:	Management Console	Assignee:	Robb Hamilton <rhamilto>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.4	CC:	aos-bugs, eparis, hasha, jokerman, mfojtik, rhamilto, scuppett, slaznick
Target Milestone:	---
Target Release:	4.4.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-04 11:20:24 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:
Embargoed:

Description Udi Kalifon 2019-12-17 10:12:39 UTC

Description of problem:
I installed a fresh cluster and created a user in the htpasswd file. The user can log in, can create new projects and deploy an app. However, when browsing over to the deployment or the replica set, and switching to the "pods" tab, you get the error: "Restricted Access". There is no problem to list pods in the Pods page with this user, so there should also be no problem listing the deployment's pods.


Version-Release number of selected component (if applicable):
4.4.0-0.ci-2019-12-14-210519


How reproducible:
100%


Steps to Reproduce:
1. Create a user and log in with it
2. Create a new project
3. Create a new application (I created hello-openshift)
4. Browse to the deployment page, select the deployment, and switch to the "Pods" tab


Actual results:
Restricted Access
pods is forbidden: User "alice" cannot list resource "pods" in API group "" at the cluster scope

Expected results:
Deployment pods should be listed


Additional info:
The cluster is a libvirt cluster simulating bare metals, installed with the dev-scripts.

Comment 1 Stephen Cuppett 2019-12-17 11:38:13 UTC

There is likely a missing role/permission rule for the created users of this auth mechanism here (and doc step to identify the need). Assigning to auth to take a look to fill in the gap.

Comment 2 Standa Laznicka 2020-01-02 09:22:57 UTC

Moving to console, `pods is forbidden: User "alice" cannot list resource "pods" in API group "" at the cluster scope` means cluster-level pods search was performed although the user expected a namespaced search. Idk whether it's intended or not.

Comment 4 shahan 2020-01-16 11:17:51 UTC

now we could see pod list under pod tab with normal user
4.4.0-0.ci-2020-01-16-103544

Comment 6 errata-xmlrpc 2020-05-04 11:20:24 UTC

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