Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add meaningful dashboard warnings during the failures on namespace provisioning when auto-provisioning is disabled and advanced authorization is enabled #22912

Closed
dipakkarde opened this issue Apr 9, 2024 · 0 comments · Fixed by eclipse-che/che-dashboard#1123
Assignees
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.

Comments

@dipakkarde
Copy link

dipakkarde commented Apr 9, 2024

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 setting auto-provisioning of namespaces turned off and setting advanced authorization as below :

 devEnvironments:
    containerBuildConfiguration:
      openShiftSecurityContextConstraint: container-build
    defaultNamespace:
      autoProvision: false                                <---------
      template: <username>-devspaces
    maxNumberOfWorkspacesPerUser: -1
    secondsOfInactivityBeforeIdling: 1800
    secondsOfRunBeforeIdling: -1
    security: {}
    startTimeoutSeconds: 300
    storage:
      pvcStrategy: per-user
$ oc get checluster devspaces -n openshift-operators -o yaml | grep -i networking -A12
  networking:
    auth:
      advancedAuthorization:                               <------------
        allowUsers:
        - test
      gateway:
        configLabels:
          app: che
          component: che-gateway-config
        kubeRbacProxy:
          logLevel: 0
        oAuthProxy:
          cookieExpireSeconds: 86400

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.

Screenshot from 2024-04-09 09-34-41

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

@dipakkarde dipakkarde added the kind/enhancement A feature request - must adhere to the feature request template. label Apr 9, 2024
@dipakkarde dipakkarde changed the title Add meaningful dashboard warnings during the failures on namespace provisioning when auto-provisioning is disabled and advanced authorization is enabled.d Add meaningful dashboard warnings during the failures on namespace provisioning when auto-provisioning is disabled and advanced authorization is enabled Apr 9, 2024
@ibuziuk ibuziuk added severity/P2 Has a minor but important impact to the usage or development of the system. area/dashboard labels Apr 9, 2024
@akurinnoy akurinnoy moved this to 📋 Backlog in Eclipse Che Team A Backlog May 14, 2024
@ibuziuk ibuziuk moved this from 📋 Backlog to 📅 Planned in Eclipse Che Team A Backlog May 16, 2024
@dmytro-ndp dmytro-ndp moved this from 📅 Planned to 🚧 In Progress in Eclipse Che Team A Backlog May 22, 2024
@dmytro-ndp dmytro-ndp moved this from 🚧 In Progress to 📅 Planned in Eclipse Che Team A Backlog May 22, 2024
@akurinnoy akurinnoy self-assigned this May 30, 2024
@akurinnoy akurinnoy moved this from 📅 Planned to 🚧 In Progress in Eclipse Che Team A Backlog May 30, 2024
@akurinnoy akurinnoy moved this from 🚧 In Progress to Ready for Review in Eclipse Che Team A Backlog Jun 5, 2024
@ibuziuk ibuziuk moved this from Ready for Review to ✅ Done in Eclipse Che Team A Backlog Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

3 participants