Chapter 4. Known issues

On IBM Z and IBM Power, the debugging features cannot be activated in the Go workspace in CodeReady Workspaces 2.15. 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.

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.

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:

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.

Currently, there is a restriction for OpenShift Dedicated and ROSA: CodeReady Workspaces must not be deployed to the openshift-workspaces namespace.

On IBM Power, the list of supported image streams is missing, which causes component creation to fail. There is currently no workaround for this issue.

Currently, upgrading a CodeReady Workspaces instance with the Dev Workspace engine enabled requires the following manual steps as a workaround:

Support for deploying CodeReady Workspaces 2.15 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.

Currently, when using OperatorHub to install CodeReady Workspaces with the Dev Workspace engine, you cannot enable the Image Puller. The Image Puller currently does not work with the tech-preview-latest-all-namespaces channel.

When using the Cake-php sample, the Configure Apache Web Server DocumentRoots task fails with the following error:

error  sed: couldn't open temporary file /etc/httpd/conf/sedSgv1Z4: Permission denied

error  sed: couldn't open temporary file /etc/httpd/conf/sedSgv1Z4: Permission denied

There is currently no workaround for this issue.

Currently, a CodeReady Workspaces instance might display an empty page after the user session expires. There is currently no workaround for this issue.

Currently, the dashboard of a CodeReady Workspaces instance might display an empty page after a server error. There is currently no workaround for this issue.