Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-2788

No useful information in case of 'no creation of namespaces' user having no namespace ready

XMLWordPrintable

    • False
    • False
    • Hide

      1. Configure CRW with CHE_INFRA_KUBERNETES_NAMESPACE_CREATION__ALLOWED set to 'false'.

      2.  Have a user (owning no current namespaces) attempt to start a new workspace.

      3.  Note that there is no good error message provided.

       

      Show
      1. Configure CRW with CHE_INFRA_KUBERNETES_NAMESPACE_CREATION__ALLOWED set to 'false'. 2.  Have a user (owning no current namespaces) attempt to start a new workspace. 3.  Note that there is no good error message provided.  

      We give the users an option called  CHE_INFRA_KUBERNETES_NAMESPACE_CREATION__ALLOWED.

      If this option has value 'false', CRW does not create a new namespace/Project when a workspace is created.  Either the user has one already created by an administrator (this namespace must have proper annotations, etc.) OR CRW will fail.

       

      In the event CRW fails, in version 2.14 an error message popped up on the user's browser.  (See attached image).  "Failed to fetch list of kubernetes namespaces...."

       

      Since 2.15, no error message appears.  The user has a 'blank' screen and no idea what is happening or how to describe it to an administrator.

       

      Please make some meaningful error message in case this happens.

        1. crw_2.14_user_namespace_not_found.PNG
          95 kB
          Rick Wagner
        2. crw_2.15_authentication_blank_page.PNG
          90 kB
          Rick Wagner
        3. crw-2.15.3.RC-03-22_ws_creation.png
          359 kB
          Dmytro Nochevnov
        4. crw-2.15.3.RC-03-22.png
          247 kB
          Dmytro Nochevnov

              okurinny Oleksii Kurinnyi
              rhn-support-rick Rick Wagner
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: