Chapter 3. Bug fixes

As of OpenShift Dev Spaces 3.3, the .NET sample project has been reintroduced. It has been updated to run with .NET version 7.

Before this update, workspaces failed to start when using a devfile that points to a private container registry. This failure occurred even though the user had added the registry in the Add Container Registry dialog in the dashboard’s User Preferences. With this update, you can start workspaces from a devfile that points to a container image in a private container registry. Before starting a workspace with such a devfile, you must add the registry in the Add Container Registry dialog in the dashboard’s User Preferences.

Before this update, a regression issue caused files in the /.vscode/ and /.che/ subfolders of the cloned remote Git repository to be ignored during workspace creation. This issue was only relevant to Git repositories that are hosted on GitHub, GitLab, or Bitbucket. With this update, files in these subfolders are fetched and processed during workspace creation.

Before this update, having the CheCluster custom resource with spec.components.imagePuller.enable: true in the prod-namespace namespace resulted in Kubernetes Image Puller Operator failing due to an invalid OperatorGroup. That was causing the following error message: Operator failed OwnNamespace InstallModeType not supported, cannot configure to watch own namespace. With this update, this issue is resolved with Kubernetes Image Puller Operator creating a correct OperatorGroup with empty targetNamespaces.

Before this update, dsc server:delete --delete-namespace deleted any namespace in which the OpenShift Dev Spaces instance had been installed, even the openshift-operators namespace if inadvertently chosen during installation. Removal of the openshift-operators namespace might result in unintended removal of other installed Operators. With this update, the dsc server:delete command with the --delete-namespace option does not remove the openshift-operators namespace.

Before this update, no error message was shown a when workspace failed to start due to a Kubernetes quota. With this update, the error is successfully displayed during workspace startup when OpenShift Dev Spaces is unable to create a workspace Pod because of an insufficient quota in the user namespace.

Before this update, workspace creation failed on OpenShift Dev Spaces if an administrator had configured to trust a Git provider’s self-signed TLS certificate with a che-git-self-signed-cert ConfigMap that lacked a githost section. The resulting /etc/gitconfig file contained a malformed http directive that didn’t match any URL. With this update, this issue is resolved, and the /etc/gitconfig file contains an [http] line as expected.

Before this update, starting a workspace with a name that was in use for another workspace resulted in the Creating a workspace page showing a Failed to create a workspace error message. With this update, the Creating a workspace page warns users of an Existing workspace found and prompts users to Open the existing workspace or Create a new workspace.