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

Can not start a workspace: configured storage type not supported #21710

Closed
Tracked by #21705
RomanNikitenko opened this issue Sep 16, 2022 · 5 comments
Closed
Tracked by #21705
Assignees
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator area/chectl Issues related to chectl, the CLI of Che engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Milestone

Comments

@RomanNikitenko
Copy link
Member

Describe the bug

I get an error at starting workspace: Failed to open the workspace. Error provisioning storage: configured storage type not supported

Che version

next (development version)

Steps to reproduce

  1. Start a minikube
  2. Go to dashboard
  3. Go to Create workspace
  4. Put https://github.com/che-incubator/che-code to the Git Repo URL field
  5. Create and Open button

Expected behavior

The workspace has started successfully

Runtime

minikube

Screenshots

image

Installation method

chectl/next

Environment

macOS

Eclipse Che Logs

No response

Additional context

No response

@RomanNikitenko RomanNikitenko added the kind/bug Outline of a bug - must adhere to the bug report template. label Sep 16, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 16, 2022
@ibuziuk
Copy link
Member

ibuziuk commented Sep 16, 2022

@RomanNikitenko could you please provide the EclipseChe CR ?

@ibuziuk ibuziuk added severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code. engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 16, 2022
@RomanNikitenko
Copy link
Member Author

RomanNikitenko commented Sep 16, 2022

EclipseChe CR
apiVersion: org.eclipse.che/v1
kind: CheCluster
metadata:
  creationTimestamp: '2022-09-16T11:57:04Z'
  finalizers:
    - checluster.che.eclipse.org
    - cheGateway.clusterpermissions.finalizers.che.eclipse.org
    - cheWorkspaces.clusterpermissions.finalizers.che.eclipse.org
    - namespaces-editor.permissions.finalizers.che.eclipse.org
    - devWorkspace.permissions.finalizers.che.eclipse.org
    - dashboard.clusterpermissions.finalizers.che.eclipse.org
  generation: 5
  managedFields:
    - apiVersion: org.eclipse.che/v2
      fieldsType: FieldsV1
      fieldsV1:
        f:spec:
          .: {}
          f:components:
            .: {}
            f:cheServer:
              .: {}
              f:debug: {}
              f:logLevel: {}
            f:database:
              .: {}
              f:credentialsSecretName: {}
              f:externalDb: {}
              f:postgresDb: {}
              f:postgresHostName: {}
              f:postgresPort: {}
              f:pvc:
                .: {}
                f:claimSize: {}
            f:metrics:
              .: {}
              f:enable: {}
          f:containerRegistry: {}
          f:devEnvironments:
            .: {}
            f:defaultComponents: {}
            f:defaultEditor: {}
            f:defaultNamespace:
              .: {}
              f:autoProvision: {}
              f:template: {}
            f:secondsOfInactivityBeforeIdling: {}
            f:secondsOfRunBeforeIdling: {}
            f:storage: {}
          f:gitServices: {}
          f:networking:
            .: {}
            f:auth:
              .: {}
              f:gateway:
                .: {}
                f:configLabels:
                  .: {}
                  f:app: {}
                  f:component: {}
              f:identityProviderURL: {}
              f:oAuthClientName: {}
              f:oAuthSecret: {}
            f:domain: {}
            f:tlsSecretName: {}
      manager: unknown
      operation: Update
      time: '2022-09-16T11:57:04Z'
    - apiVersion: org.eclipse.che/v2
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:finalizers:
            v:"dashboard.clusterpermissions.finalizers.che.eclipse.org": {}
        f:status:
          f:pluginRegistryURL: {}
      manager: manager
      operation: Update
      time: '2022-09-16T11:58:39Z'
    - apiVersion: org.eclipse.che/v2
      fieldsType: FieldsV1
      fieldsV1:
        f:status:
          f:chePhase: {}
          f:cheURL: {}
          f:cheVersion: {}
          f:gatewayPhase: {}
          f:workspaceBaseDomain: {}
      manager: manager
      operation: Update
      subresource: status
      time: '2022-09-16T12:00:40Z'
    - apiVersion: org.eclipse.che/v1
      fieldsType: FieldsV1
      fieldsV1:
        f:spec:
          f:storage:
            f:pvcStrategy: {}
      manager: dashboard
      operation: Update
      time: '2022-09-16T13:22:01Z'
  name: eclipse-che
  namespace: eclipse-che
  resourceVersion: '43301'
  uid: 4f9285ab-1187-4459-99e8-673f4901cdc6
spec:
  auth:
    externalIdentityProvider: false
    identityProviderContainerResources:
      limits: {}
      request: {}
    identityProviderIngress: {}
    identityProviderRoute: {}
    identityProviderURL: http://dex.dex:5556
    oAuthClientName: eclipse-che
    oAuthSecret: EclipseChe
    updateAdminPassword: false
  dashboard: {}
  database:
    chePostgresContainerResources:
      limits: {}
      request: {}
    chePostgresDb: dbche
    chePostgresHostName: postgres
    chePostgresPort: '5432'
    chePostgresSecret: postgres-credentials
    externalDb: false
    postgresVersion: '13.3'
    pvcClaimSize: 1Gi
  devWorkspace:
    enable: true
    secondsOfInactivityBeforeIdling: 1800
    secondsOfRunBeforeIdling: -1
  gitServices: {}
  imagePuller:
    enable: false
    spec: {}
  k8s:
    ingressDomain: 192.168.64.24.nip.io
    tlsSecretName: che-tls
  metrics:
    enable: true
  server:
    allowAutoProvisionUserNamespace: true
    allowUserDefinedWorkspaceNamespaces: false
    cheDebug: 'false'
    cheLogLevel: INFO
    cheServerIngress: {}
    cheServerRoute: {}
    dashboardIngress: {}
    dashboardRoute: {}
    devfileRegistryIngress: {}
    devfileRegistryRoute: {}
    externalDevfileRegistry: false
    externalPluginRegistry: false
    gitSelfSignedCert: false
    openVSXRegistryURL: https://open-vsx.org
    pluginRegistryIngress: {}
    pluginRegistryRoute: {}
    selfSignedCert: false
    singleHostGatewayConfigMapLabels:
      app: che
      component: che-gateway-config
    tlsSupport: false
    useInternalClusterSVCNames: false
    workspaceDefaultComponents:
      - container:
          image: quay.io/devfile/universal-developer-image:ubi8-38da5c2
          sourceMapping: /projects
        name: universal-developer-image
    workspaceDefaultEditor: eclipse/che-theia/latest
    workspaceNamespaceDefault: <username>-che
  storage:
    preCreateSubPaths: false
    pvcStrategy: per-user
status:
  cheClusterRunning: Available
  cheURL: https://192.168.64.24.nip.io
  cheVersion: next
  dbProvisioned: false
  devfileRegistryURL: https://192.168.64.24.nip.io/devfile-registry
  devworkspaceStatus:
    gatewayHost: 192.168.64.24.nip.io
    gatewayPhase: Established
    phase: Active
    workspaceBaseDomain: 192.168.64.24.nip.io
  gitHubOAuthProvisioned: false
  gitServerTLSCertificateConfigMapName: ''
  keycloakProvisioned: false
  keycloakURL: ''
  openShiftoAuthProvisioned: false
  pluginRegistryURL: https://192.168.64.24.nip.io/plugin-registry/v3

@AObuchow
Copy link

I was able to reproduce this issue, looking into it.

@AObuchow
Copy link

It seems that DWO version 15.2 is being used in the chectl deployment of che, and this version does not include devfile/devworkspace-operator#893

@AObuchow
Copy link

@ibuziuk and I discussed that chectl needs to use an updated image of DWO, and chectl nightly should probably use the nightly build of DWO.
cc: @tolusha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/che-operator Issues and PRs related to Eclipse Che Kubernetes Operator area/chectl Issues related to chectl, the CLI of Che engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/bug Outline of a bug - must adhere to the bug report template. severity/blocker Causes system to crash and be non-recoverable or prevents Che developers from working on Che code.
Projects
None yet
Development

No branches or pull requests

5 participants