This documentation is for a release that is no longer maintained
See documentation for the latest supported version.Dieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 7. Known issues
7.1. Upgrading OpenShift Dev Spaces from 3.5 to 3.6 might require manual steps Link kopierenLink in die Zwischenablage kopiert!
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
- Go to the OpenShift web console.
Delete your existing Red Hat OpenShift Dev Spaces Operator subscription and the
devspacesCSV.NoteThis does not remove any of the deployed pods or running workspaces.
- Install the latest Red Hat OpenShift Dev Spaces Operator subscription.
- 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
7.2. Duplicate workspaces cannot be created after upgrading from OpenShift Dev Spaces 3.4 Link kopierenLink in die Zwischenablage kopiert!
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
generateNamerather thanfixedNameto 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 Link kopierenLink in die Zwischenablage kopiert!
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.
This known issue does not impact Git-provider OAuth that has been configured by administrators.
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>
git commit config --global user.name <your_name> git commit config --global user.email <your_email>Copy to Clipboard Copied! Toggle word wrap Toggle overflow
Additional resources
7.4. Debugger does not work in the .NET sample Link kopierenLink in die Zwischenablage kopiert!
Currently, the debugger in Microsoft Visual Studio Code - Open Source does not work in the .NET sample.
Workaround
Use a different image that is available from the following sources:
Additional resources
7.5. New workspaces based on Bitbucket.org-hosted repositories fail to start without a v2 devfile Link kopierenLink in die Zwischenablage kopiert!
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
- If the repository does not contain a devfile, add a v2.1 devfile to the repository.
- If the repository contains a v1 devfile, migrate the devfile from v1 to v2.1. See https://devfile.io/docs/2.1.0/migrating-to-devfile-v2.
Additional resources