Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.

Chapter 7. Known issues


There is a known issue when updating to version 3.6: clusters that were updated to devspacesoperator.v3.5.0-0.1682130576.p require additional steps from administrators as a workaround.

Workaround

  1. Go to the OpenShift web console.
  2. Delete your existing Red Hat OpenShift Dev Spaces Operator subscription and the devspaces CSV.

    Note

    This does not remove any of the deployed pods or running workspaces.

  3. Install the latest Red Hat OpenShift Dev Spaces Operator subscription.
  4. Wait until all pods are replaced by new ones before opening the dashboard or loading workspaces.

Alternatively, you can use the oc command-line tool.

Additional resources

Currently, users are unable to create multiple workspaces from the same dashboard sample or Git repository URL after upgrading OpenShift Dev Spaces from version 3.4.

Administrators must ask users before the upgrade to push their latest workspace changes to their Git repositories and to be prepared to delete and recreate workspaces after the upgrade.

Workaround

Use a relevant option:

  • Update your devfile with generateName rather than fixedName to have a unique name generated for each new workspace.
  • Delete any previous workspaces from the same sample or Git repository before creating a new one.

Additional resources

7.3. Incorrect user name and email in commit messages for some users

There is currently a known issue for users who are using a Kubernetes Secret with their Git-provider credentials. The user name and email for Git operations in worspaces for those users are currently taken from the user-profile Secret of the <user>-devspaces namespace.

Important

Workaround

  • In the editor terminal of the running workspace, run the following commands to set your commit author name and email:

    git commit config --global user.name <your_name>
    git commit config --global user.email <your_email>
    Copy to Clipboard Toggle word wrap

Additional resources

7.4. Debugger does not work in the .NET sample

Currently, the debugger in Microsoft Visual Studio Code - Open Source does not work in the .NET sample.

Workaround

Additional resources

Currently, new workspaces based on a Bitbucket.org-hosted repository fail to start if the repository contains no devfile or a v1 devfile. The result is the Failed to create the workspace error message.

Workaround

Additional resources

Nach oben
Red Hat logoGithubredditYoutubeTwitter

Lernen

Testen, kaufen und verkaufen

Communitys

Über Red Hat Dokumentation

Wir helfen Red Hat Benutzern, mit unseren Produkten und Diensten innovativ zu sein und ihre Ziele zu erreichen – mit Inhalten, denen sie vertrauen können. Entdecken Sie unsere neuesten Updates.

Mehr Inklusion in Open Source

Red Hat hat sich verpflichtet, problematische Sprache in unserem Code, unserer Dokumentation und unseren Web-Eigenschaften zu ersetzen. Weitere Einzelheiten finden Sie in Red Hat Blog.

Über Red Hat

Wir liefern gehärtete Lösungen, die es Unternehmen leichter machen, plattform- und umgebungsübergreifend zu arbeiten, vom zentralen Rechenzentrum bis zum Netzwerkrand.

Theme

© 2025 Red Hat