Chapter 4. Known issues

On IBM Z and IBM Power Systems, the debugging features cannot be activated in the Go workspace in CodeReady Workspaces 2.12. Delve, the required debugger for the Go programming language, is not available for these platforms. An attempt to activate this feature results in the Failed to continue error message. This issue has no workaround.

Golang based workspaces do not include basic language server features such as code autocompletion.

A lack of OpenShift Container Platform cluster resources causes a failure. This failure causes a misleading message: Your session has expired. Please, log in to CodeReady Workspaces again to get access to your OpenShift account.

When using the single-host strategy for workspace exposure, attempting to clone a workspace from a Quick Add sample results in an error. There is currently no workaround for this issue.

The crwctl binaries do not run on IBM Z and IBM Power Systems. These platforms are available as targets for deploying CodeReady Workspaces.

CodeReady Workspaces might fail to create a workspace when the network is unstable. CodeReady Workspaces displays an error such as the following: Failed to run the workspace: "Waiting for pod 'workspace9fbid1gnx7273d47.maven-545f8c9cf4-hw79f' was interrupted." This issue has no workaround.

The following devfiles are not supported on IBM Z and IBM Power Systems:

Support for deploying CodeReady Workspaces on OpenShift Container Platform on IBM Z is available as a Technology Preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not fully function. Red Hat does not suggest using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

When starting a workspace, users might receive the following error message: Your session has expired. Please login to Che again to get access to your OpenShift account.

A workspace using Java with the JBoss EAP 7.3 devfile fails with the following error message: No delegateCommandHandler for vscode.java.startDebugSession. There is no workaround for this issue.

When a task is running and there is some networking issue, the terminal window is cleared and contains no text. Even when the connection is restored, the terminal remains empty and loading. There is no workaround for this issue.

The OpenShift Connector plug-in fails to deploy because of the inability to access the odo image in the disconnected environment. There is no workaround for this issue.

The DEBUG panel displays No Configurations in the drop-down list because no configurations are loaded.

After patching the CodeReady Workspaces 2.12 instance from multi-host to single-host, the Dashboard Create Workspace page displays an incomplete UI with missing icons.

Don’t deploy CodeReady Workspaces to the openshift-workspaces namespace on OpenShift Dedicated and ROSA.

Upstream sample devfiles are designed for Eclipse Che. CodeReady Workspaces doesn’t support these samples. A workspace running with the Dev Workspace engine might fail to start when using an upstream sample devfile.

On IBM Power Systems, the list of supported image streams is missing, which causes component creation to fail.

When the Kubernetes Image Puller is installed, uninstalling CodeReady Workspaces fails, meaning:

Support for deploying CodeReady Workspaces 2.12 with the Dev Workspace engine is available as a Technology Preview feature, for OpenShift Container Platform 4.8. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not fully function. Red Hat does not suggest using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

The Git: Clone IDE command does not work.

After deploying the CodeReady Workspaces Operator form the tech-preview Operator channel in the default namespace and creating a CheCluster Custom Resource in the default namespace, the OpenShift Prometheus UI doesn’t display the metrics.

The OpenShift Container Platform console displays confusing names in the backup related tabs. CheBackupServerConfigurations appears rather than the expected name: CodeReady Workspaces instance Specification, CodeReady Workspaces Backup Server, CodeReady Workspaces Backup Specification or CodeReady Workspaces Restore Specification . This issue has no workaround.

Upgrading an instance with the Dev Workspace engine enabled requires manual steps.

Support for deploying CodeReady Workspaces 2.12 with the Dev Workspace engine is available as a Technology Preview feature, for OpenShift Container Platform 4.8. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not fully function. Red Hat does not suggest using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

After adding a ConfigMap to a CodeReady Workspaces instance, the keycloak and codeready Pods do not restart automatically.

When the Dev Workspace engine is enabled, uninstalling CodeReady Workspaces fails, meaning: