Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 7. Known issues

Currently, redeploying the DevWorkspace Operator fails after running the dsc server:delete --delete-all command.

Workaround

  1. Delete the remaining DevWorkspace Operator resources: 

    workspaces=$(oc get devworkspaces --all-namespaces | awk 'NR>1 {print $1}') \
  && for workspace in $workspaces ; do \
       oc patch devworkspaces/$workspace -p '{ "metadata": { "finalizers": null }}' --type merge || true; \
       oc delete devworkspaces/$workspace || true; \
     done \
  && oc delete crd/devworkspaces.workspace.devfile.io
    Note

    If the oc delete crd/devworkspaces.workspace.devfile.io command fails, you must deep clean your OpenShift cluster.

  2. Redeploy the DevWorkspace Operator.

Additional resources

Currently, there is a known issue with the in-browser Visual Studio Code editor in workspaces. This happens when you create more than one workspace with the same name. Visual Studio Code does not display pop-up notifications about recommended extensions and the dialog Do you trust the authors of the files in this folder?. Also, Visual Studio Code automatically reopens the last opened files from the previous workspace of the same name. There is currently no workaround for this issue.

Additional resources

Currently, starting a new workspace fails when entering the URL of a Git repository that does not contain a devfile and specifying the Technology Preview editor, Visual Studio Code. The error message states the following reason: Unable to resolve che-code plugins: Not able to find any dev container component in DevWorkspace. There is currently no workaround for this issue.

Additional resources

There is currently a known issue when starting workspaces that clone private Git repositories. After successfully cloning and reading the remote Git repository, the project-clone container fails to checkout a specified Git revision, for example a feature branch or PR branch. As a result of this error, the remote Git repository is cloned into a temporary directory named project-clone-<random_characters>.

Note

In OpenShift Dev Spaces, users have two ways to specify a Git revision for a new workspace:

  • By adding a checkoutFrom section in the devfile.
  • By visiting or entering the URL of a feature branch or pull request in the browser or in the OpenShift Dev Spaces dashboard.

Workaround

  • If you are using a checkoutFrom section in the devfile, then do as follows:

    1. Before starting a new workspace, remove or comment out the checkoutFrom section from the devfile.
    2. After the repository is cloned, switch to the desired revision.

  • If you are using the URL of a feature branch or pull request to start a new workspace, then do as follows:

    1. When starting a new workspace, enter the URL of the repository without any branch syntax.
    2. After the repository is cloned, switch to the desired revision.

Additional resources

Currently, pulling of a private container image fails when the image is pulled from a container registry that was added in the dashboard, User Preferences Add Container Registry.

Workaround

  1. Delete the devworkspace-container-registry-dockercfg Secret: 

    $ oc delete secret devworkspace-container-registry-dockercfg -n <openshift_project>

  2. Create a new devworkspace-container-registry-dockercfg Secret: 

    $ oc create secret docker-registry devworkspace-container-registry-dockercfg --docker-username=<username> --docker-password=<password> -n <openshift_project>

  3. Edit the metadata of the new Secret: 

      labels:
    controller.devfile.io/devworkspace_pullsecret: 'true'
    controller.devfile.io/watch-secret: 'true'

Additional resources

7.6. Workspace starting and deletion might fail
Copy link

Currently, a workspace might fail to start, and then you might be unable to delete it. This is caused by a persistent volume claim (PVC) issue. Subsequently, the same problem occurs with other workspaces.

Workaround

  1. Remove the DevWorkspace object of the first stuck workspace.
  2. Remove the PVC that is bound to the invalid volume.

Additional resources

Currently, there is a known issue with the Java Gradle sample in restricted environments. Running the 1-build command to build an application might result in the FAILURE: Build failed with an exception error and failure to load a native library or not resolving a plug-in artifact in plug-in repositories. There is currently no workaround for this issue.

Additional resources

Currently, the name of the CheCluster custom resource remains the same as before upgrading from CodeReady Workspaces 2.15 to OpenShift Dev Spaces 3.2. Customers whose Checluster custom resource name is codeready-workspaces before the upgrade will find the same name after the upgrade. There is currently no workaround for this issue.

Additional resources

Currently, the Account page in the dashboard remains for display purposes only. To edit user profile, users must do so within OpenShift, because OpenShift OAuth is used for user management in OpenShift Dev Spaces.

Additional resources

Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2026 Red HatBack to top