Bug 1840355

Summary:	self-provisioner cannot find command line terminal workspace
Product:	OpenShift Container Platform	Reporter:	cvogt
Component:	Dev Console	Assignee:	cvogt
Status:	CLOSED ERRATA	QA Contact:	Gajanan More <gamore>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.5	CC:	aos-bugs, nmukherj
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:41:51 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 cvogt 2020-05-26 19:02:18 UTC

Description of problem:
A user with only self-provisioner access is unable to list workspace resources at the cluster scope. Therefore they always get an error when trying to open the command line terminal

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce:
1. install the che-workspace-controller to enable the command line terminal
2. create a user with only self-provisioner access
3. open the command line terminal

Actual results:
User gets an error that they cannot list workspaces at the cluster scope.

Expected results:
All users should be able to use the command line terminal. (except kubeadmin as there is currently a limitation on users with such access)

Reproducibility (Always/Intermittent/Only Once):
always for self-provisioner

Build Details:
4.5

Comment 5 Gajanan More 2020-06-08 09:24:55 UTC

I have validated the bugzilla on:
Build: 4.5.0-0.nightly-2020-06-05-214616
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified.

Comment 6 errata-xmlrpc 2020-07-13 17:41:51 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:2409