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

Persistent home not working with per-workspace storage type

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Hide
      = Persistent Home does not work with per-workspace storage strategy

      Previously, the `persistUserHome` CheCluster Custom Resource property was not working with the per-workspace storage strategy. The defect has been fixed in this release and now you can use the `persistUserHome` option with both the `per-user` and the `per-workspace` storage strategies.

      Find more details about the property in the official link:https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.13/html/administration_guide/configuring-devspaces#checluster-custom-resource-fields-reference[documentation].
      Show
      = Persistent Home does not work with per-workspace storage strategy Previously, the `persistUserHome` CheCluster Custom Resource property was not working with the per-workspace storage strategy. The defect has been fixed in this release and now you can use the `persistUserHome` option with both the `per-user` and the `per-workspace` storage strategies. Find more details about the property in the official link: https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.13/html/administration_guide/configuring-devspaces#checluster-custom-resource-fields-reference [documentation].
    • Bug Fix
    • Done

      Description of problem:

      Persistent user home directory feature (spec.devEnvironments.persistUserHome) does not seem to work with the per-workspace storage strategy.

      Prerequisites (if any, like setup, operators/versions):{}

      Dev Spaces 3.11, DWO 0.26.0

      Steps to Reproduce

      1. Set the following in the CheCluster CR:

      spec:  
        devEnvironments:
          storage:
            pvcStrategy: per-workspace
          persistUserHome:
            enabled: true 

      2. Start an empty workspace.

      3. In the workspace pod's spec, verify that there is no persistent-home volume:

      $ oc get pod <PODNAME> -o=jsonpath='{.spec.containers[0].volumeMounts[*]}'| grep home

      The command above should find no matches.

      Actual results:
      There is no volumeMount for the tooling container for the home directory.

       

       

      Expected results:

      There should be a volumeMount for the tooling container for the home directory.

      Reproducibility (Always/Intermittent/Only Once):

      Acceptance criteria: 

       

      Definition of Done:

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

       

       *

            aobuchow Andrew Obuchowicz
            dakwon@redhat.com David Kwon
            Serhii Skoryk Serhii Skoryk
            Jana Vrbkova Jana Vrbkova
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: