Chapter 3. Bug fixes

Before this update, Git Large File Storage (LFS) was failing on the OpenShift Dev Spaces instances that used DevWorkspace Operator 0.15. It failed because the /etc/gitconfig file that contained the git-lfs configuration was automatically overwritten to set the name and email in Git commits in the workspace. With this update, upgrading DevWorkspace Operator to 0.16 resolves this issue.

Before this update, the dashboard might fail to automatically redirect to the IDE during workspace startup, which required manually reloading the browser tab. With this update, the dashboard automatically redirects to the IDE during workspace startup.

With this update, the OpenShift Lifecycle Manager treats the DevWorkspace Operator as a OpenShift Dev Spaces dependency, and the Red Hat OpenShift Dev Spaces Operator no longer deploys or manages the DevWorkspace Operator. This enhancement prevents occurrence of multiple deployments of the DevWorkspace Operator and avoids broken webhooks in an unsupported additional DevWorkspace Operator in the devworkspace-controller namespace.

Before this update, the rollback.sh script failed to roll back the migration from Dev Spaces to CodeReady Workspaces when rollback.sh was run directly after 1-prepare.sh. After this update, the rollback.sh script successfully rolls the migration back directly after 1-prepare.sh.

Before this update, the Bitbucket API client failed to resolve the server URI because of the path segments. With this update, the server URI is successfully resolved with the path segments.

Before this update, starting a new workspace by entering the URL of a Bitbucket.org-hosted public repository failed. With this update, you can successfully start a new workspace by entering the URL of a Bitbucket.org-hosted public repository that you want to be cloned into the workspace.

Before this update, the admin users were unable to deploy applications from a Dev Spaces workspace to OpenShift because those users' default projects were not defined. This problem affected all devfiles that projected an example command to deploy the application to OpenShift, including the Node.js devfiles. With this update, when you run the deploy command included with the sample devfile projects, the Dev Spaces workspace project is selected automatically, which resolves the issue.