Chapter 3. Bug fixes

Before this update, when workspaces failed to start due to insufficient CPU or memory in available cluster nodes, there was a UI delay in notifying the user. The dashboard Progress tab remained at Waiting for workspace to start until the workspace startup timeout, and only then the error message Failed to open the workspace appeared. With this update, the Dev Workspace Operator aborts workspace startup if it detects an unschedulable condition and then quickly displays the following error message: Failed to open the workspace: Pod is unschedulable: <reasons_and_statuses>.

Before this update, the developer could be logged out unexpectedly because the session expired. With this update, the issue is resolved.

Before this update, legacy CatalogSource objects used by the Operator Lifecycle Manager (OLM) could enter a crashing state on OpenShift 4.12. This issue affected clusters with [rh-os-devspaces] 3.3 and below with container builds enabled. With this update, the issue is fixed.