Chapter 3. Bug fixes

Previously, there was a defect related to the connection to the Lightspeed service when you used the Ansible extension. Following error message would appear: "Error: invalid_request. Invalid redirect URI." This defect has been fixed in this release.

Previously, postStart commands were executed based on alphabetical order rather than the sequence in which they were listed in the devfile, leading to potential confusion, especially when a specific execution order is expected based on the listed sequence. Starting from this release, the execution happens in sequential order in the way the commands are listed in the postStart section of a devfile:

postStart:
  - command-one
  - command-two
  - command-three

Previously, setting disableWorkspaceCaBundleMount: true property in the Custom Resource (CR) did not stop mounting certificates into /etc/pki/ca-trust/extracted/pem/ directory. The defect has been fixed in this release.

Previously, when you deleted a workspace while using the per-user PVC strategy, the workspace might not have been deleted correctly if another workspace was running. In this release, a warning message will appear in such situations with a suggestion to stop running workspaces before you delete any.

Previously, when accepting Bitbucket server’s OAuth2 prompt, there was an unexpected error redirect page with the error stack trace: {"message":"Cannot invoke \"String.length()\" because \"this.input\" is null","trace"}. The defect has been fixed in this release.

The regression related to the controller.devfile.io/storage-type: ephemeral attribute has been fixed in this release, and Cloud Development Environments (CDEs) created from devfiles with this attribute now correctly use the emptyDir volumes.

Previously, there was a defect related to the loss of all Git history if a workspace pod was restarted with a default devfile when the persistent storage strategy specified in the CheCluster was per-workspace. The defect has been fixed in this release.

Before this release, it was not possible to use the desktop version of the JetBrains IntelliJ IDEA to connect to a workspace with a ubi9-based image over the JetBrains Gateway application. This defect has been fixed with this release.