Chapter 4. Known issues

4.1. Debugging cannot be activated in Go workspaces on IBM Z and IBM Power Systems

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.

Workaround

  • Delve debugger is not available for IBM Z and IBM Power Systems architectures, therefore cannot be used.

Additional resources

4.2. Language server features are not preinstalled in the Go workspace

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

Procedure

  1. Run the CodeReady Workspaces instance in a non-restricted environment.
  2. Install the required module using the Install button of the pop-up window in the IDE.

Additional resources

4.3. Misleading error message for a workspace failure caused by the mkdir Pod timeout

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.

Workaround

  • Provide more resources to the OpenShift Container Platform cluster.

Additional resources

4.4. Starting the same task multiple times doesn’t work properly

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.

Workaround

  • Execute a task in the My workspace environment once.

Additional resources

4.5. Get-Started devfiles have incorrect source location

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

Additional resources

4.6. The location of the Get Started devfiles is not calculated properly when an external devfile registry is specified

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.

Example 4.1. Deployment using multiple registries

The Developer Sandbox enables the community registry and the CodeReady Workspaces registry.

Workaround

  • Build the registries specifying one unique registry.

Additional resources

4.7. crwctl binaries are unsupported on IBM Z and IBM Power Systems

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.

Workaround

  • Run crwctl from a supported platform.

Additional resources

4.8. Unsupported devfiles on IBM Z and IBM Power Systems

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

  • EAP for OpenJDK 8
  • .Net
  • Fuse

Workaround

  • Don’t use unsupported languages on IBM Z and IBM Power Systems.

Additional resources

4.9. Technology preview support for IBM Power Systems and IBM Z

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.

Additional resources

4.10. Failed to run the Apache Camel language server

The activation of the Apache Camel 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.

Additional resources