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

Do not wait for PV state bound if we got a message "waiting for the first consumer to be created before binding" #13437

XMLWordPrintable

      Part 1:

      When default StorageClass is configured to have volumeBindingMode set to WaitForFirstConsumer, workspaces do not start. I guess that's because che is waiting for PVC to be in "Bound" state before creating workspace (or mkdir) pod. But this is not happening with this volumeBindingMode and the PVC is stuck in "Pending" state with message "waiting for first consumer to be created before binding" until the workspace startup fails.

      Reproduction Steps
      Create default StorageClass with WaitForFirstConsumer volumeBindingMode (more info here)
      Try to start workspace
      Workspace startup fails with message:

      Error: Failed to run the workspace: "Waiting for persistent volume claim 'claim-che-workspace' reached timeout"

      Part 2:

      Do not wait for PV state bound if we got a message "waiting for the first consumer to be created before binding"
      Follow up #12889

      More info:

              skabashn Sergii Kabashniuk
              psrna Pavol Srna
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: