Cause: The createProjectMessage was being used in an alert, but the default message did not provide sufficient information.
Consequence: Users without self provisioning or any projects available would see a vague message on the projects list page.
Fix: Update the content of the alert shown on the projects list page.
Result: A better message is shown on the projects list page and users will have a better idea of how to move forward.
Created attachment 1638837[details]
Error message
See screenshot. We should show something other "You may not request a new project via this API." or at least something in addition to that.
1. Remove self provisioning for authenticated user
oc edit clusterrolebindings self-provisioners // remove these 4 lines
subjects:
- apiGroup: rbac.authorization.k8s.io
kind: Group
name: system:authenticated:oauth
clusterrolebinding.rbac.authorization.k8s.io/self-provisioners edited
2. User login to console, you will see message
To get started, you'll need a project. Currently, you can't create or access any projects. You'll need to contact a cluster administrator for help. No 'Create Project' button
Verified on 4.4.0-0.nightly-2019-11-25-183933
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
Created attachment 1638837 [details] Error message See screenshot. We should show something other "You may not request a new project via this API." or at least something in addition to that.