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.9. 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.

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.

These devfiles are not supported on IBM Z and IBM Power Systems:

Support for deploying CodeReady Workspaces on OpenShift Container Platform on IBM Power Systems and 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 VS Code Tooling for Apache Camel K by Red Hat plug-in fails with the message:

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