Chapter 3. Bug fixes
3.1. Workspace not starting when both Bitbucket PAT and Bitbucket OAuth are configured
Before this update, including a Bitbucket Personal Access Token (PAT) in workspaces on a OpenShift Dev Spaces installation with Bitbucket OAuth integration resulted in a "Backend is not available" error message. With this update, the workspace starts without issues.
Additional resources
3.2. Devfile not resolved on private GitLab repositories
Before this update, OpenShift Dev Spaces failed to find devfiles at the root of GitLab private repositories. This update solves the issue.
Additional resources
3.3. Ignored volumes size in devfiles
Before this update, there was an issue with volume sizes in devfiles being ignored. With this update, if at least one volume in a DevWorkspace specifies its size, and the computed PVC size is greater than the default per-workspace PVC size, the computed PVC size will be used.
Additional resources
3.4. Devfile of Azure DevOps Git repositories URLs ending with .git not resolving
Before this update, OpenShift Dev Spaces failed to find the devfile.yaml
in Azure DevOps Git repositories when the provided URL ended with the .git
suffix. This behavior has been addressed in this release.
Additional resources
3.5. Subtle "Existing Workspaces" visual glitch
Before this update, you could experience the page blinking shortly when navigating to the "Existing Workspace" page on OpenShift Dev Spaces User Dashboard. This has been addressed in this release.
Additional resources
3.6. Workspace creation resulting in a "409 Conflict" error
Before this update, the User Dashboard would sometimes create a workspace twice resulting in the "409 Conflict" error. This behavior has been addressed in this release.
Additional resources
3.7. Workspace startup failed when the file name of a raw devfile was different from devfile.yaml
Before this update, workspace startup failed when the file name of the raw devfile was not devfile.yaml
or .devfile.yaml
. With this update, the name of the raw devfile does not prevent a successful workspace startup.
Additional resources
3.8. Downloading project zip file from an external devfile registry fails
Before this update, downloading a project zip file from an external devfile registry failed with an "x509: certificate signed by unknown authority" error. With this update, the project-clone
init container reads any .crt
or .pem
files stored in /public-certs
. These certificates are added to the HTTP client used for preparing zip-based projects in a DevWorkspace and allow you to download project zips from default-untrusted sources by e.g. auto-mounting certificates to /public-certs
in the container.
Additional resources
3.9. Failures in route creation
Before this update, there were failures in route creation. With this update, the handling of routing in the DevWorkspace operator is improved.
Additional resources
3.10. Granting extra permissions breaks Bitbucket SaaS OAuth flow
Before this update, granting extra permissions to the Bitbucket OAuth application broke the workspace startup flow. With this update, the issue is fixed.
Additional resources
3.11. Allow devfile without metadata
Before this update, it was not possible to start workspaces based on Devfiles that did not contain metadata. With this update, devfiles without .metadata.name
are considered valid. This is consistent with the specification.
Additional resources
3.12. Workspace URL parameters missing after accepting OAuth authorization
Before this update, OpenShift Dev Spaces was missing factory URL parameters after successful OAuth authentication. This resulted in the workspace not starting. With this update, the issue is fixed.
Additional resources
3.13. GitLab OAuth tokens not refreshed on workspace restart
Before this update, GitLab OAuth tokens expired after 2 hours and were not refreshed after a workspace restart. With this update, the issue is fixed.
Additional resources
3.14. Changes in workspace disappearing after 'Restart with default devfile'
Before this update, the ephemeral mode was used for the 'Restart with default devfile' functionality. When restarted, any changes in the workspace were lost. With this update, restarting the workspace with the default devfile does not erase changes you made previously.
Additional resources