Add meaningful dashboard warnings during the failures on namespace provisioning when auto-provisioning is disabled and advanced authorization is enabled #22912
Labels
area/dashboard
kind/enhancement
A feature request - must adhere to the feature request template.
severity/P2
Has a minor but important impact to the usage or development of the system.
Is your enhancement related to a problem? Please describe
I have a customer with below concern :
Customer is using
OpenShift DevSpaces 3.12.0
and settingauto-provisioning
of namespaces turned off and settingadvanced authorization
as below :After this when tried creating a sample workspace with kubeadmin user, But was not able to access the workspace with and was getting below errors in upper right corner :
Automatic namespace provisioning is disabled. Namespace might note have been configured yet. Please contact the administrator.
Advanced authorization is enabled. User might not be allowed. Please, contact the administrator.
and in middle of the screen we get below error :
HTTP Error code 500. Endpoint which throws an error https://devspaces.apps.occ.cc.corp/api/kubernetes/namespace/provision. Check the browser logs message.
Describe the solution you'd like
Customer Expectation :
The error message in the upper right corner is correct.
But they don't like the error message in the middle of the screen:
HTTP Error code 500. Endpoint which throws an error https://devspaces.apps.occ.cc.corp/api/kubernetes/namespace/provision. Check the browser logs message.
Their request is that this "ugly" message should be replaced with a more user-friendly message, that is, messages like:
Automatic namespace provisioning is disabled. Namespace might note have been configured yet. Please contact the administrator.
or
Advanced authorization is enabled. User might not be allowed. Please, contact the administrator.
Should be displayed in the middle of the screen instead of the top right corner.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: