Chapter 4. Known issues

Delve, a debugger for the Go programming language, is not available for IBM Z and IBM Power Systems architecture. Therefore, debugging features cannot be activated in the Go workspace in CodeReady Workspaces 2.10. An attempt to activate this feature results in the Failed to continue error message.

In a workspace created using the default Go devfile, some features fail because additional tools are missing. For instance, Auto-complete is unavailable.

The failure caused by a lack of OpenShift Container Platform cluster resources is accompanied by a misleading error message:

Your session has expired. Please, log in to CodeReady Workspaces again to get access to your OpenShift account.

This message will be fixed in the upcoming release.

If you start a task from My workspace multiple times, the task doesn’t end properly. The IDE displays a spinning-wheel icon as a replacement for the "✓" marker. As a consequence, the subsequent task execution can’t be started.

CodeReady Workspaces fails to run the PHP debug. PHP is a technology preview feature.

Get-Started devfiles have incorrect source location after the switch from multi-host to single-host exposure strategy.

When building the devfile registry, the build process updates the devfiles to set the source location of the artifact archives. When specifying multiple registries, the build process doesn’t update the archive source location in the devfiles properly.

The crwctl binaries don’t run on IBM Z and IBM Power Systems. These platforms are available uniquely as targets to deploy CodeReady Workspaces to.

CodeReady Workspaces is intermittently failing to create a workspace when the network is unstable. CodeReady Workspaces displays following error:

Failed to run the workspace: "Waiting for pod 'workspace9fbid1gnx7273d47.maven-545f8c9cf4-hw79f' was interrupted."

These 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 be functionally complete. 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 activation of the Appliance for Apache Camel K by Red Hat extension fails with the error message:

Activating extension `Appliance for Apache Camel K by Red Hat` failed: Dependent extension `redhat.vscode-commons` is not installed.

CodeReady Workspaces fails to start a workspace with a factory when the workspace is defined using the devfile 2.0 (DevWorkspace) specification. Then, CodeReady Workspaces displays the following error message:

Getting workspace detail data failed. Failed to fetch the workspace sprin-petclinic, reason: Could not retrieve the main URL for the running workspace.

The Python language server functionality does not work, and an error message is displayed while invoking the autocomplete and error highlighting functions.

The OpenShift Connector plug-in fails to deploy because of the inability to access the odo image in the disconnected environment.

Debug configurations are not loaded. The Debug panel displays:

No Configurations

After patching a CodeReady Workspaces 2.10 instances from multi-host to single-host, the "Create Workspace" Dashboard page displays incomplete UI with missing icons.

Bitbucket factory URL fails for public repositories outside OpenShift Container Platform for CodeReady Workspaces without Bitbucket OAuth enabled.