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.10. An attempt to activate this feature results in the
Failed to continue error message.
- Delve debugger is not available for IBM Z and IBM Power Systems architectures, therefore cannot be used.
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.
- Run the CodeReady Workspaces instance in a non-restricted environment.
- Install the required module using the Install button of the pop-up window in the IDE.
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.
- Provide more resources to the OpenShift Container Platform cluster.
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.
- Execute a task in the My workspace environment once.
4.5. Failing to run the PHP debug
CodeReady Workspaces fails to run the PHP debug. PHP is a technology preview feature.
4.6. 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.
4.7. 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.
- Build the registries specifying one unique registry.
crwctl binaries are unsupported on IBM Z and IBM Power Systems
crwctl binaries don’t run on IBM Z and IBM Power Systems. These platforms are available uniquely as targets to deploy CodeReady Workspaces to.
crwctlfrom a supported platform.
4.9. Workspace creation failing on unstable networks
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."
4.10. 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
- Don’t use unsupported languages on IBM Z and IBM Power Systems.
4.11. Technology preview support for IBM Z
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.
4.12. Failing to activate the
Appliance for Apache Camel K by Red Hat extension
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.
4.13. Could not start a workspace with factory using devfile 2.0 specification
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.
- Navigate to the DevWorkspace details
Edit the DevWorkspace YAML to set the endpoints attributes type to
endpoints: - attributes: type: main
- Restart the DevWorkspace.
4.14. The autocomplete and Error highlighting function does not work in Python devfile workspaces
The Python language server functionality does not work, and an error message is displayed while invoking the autocomplete and error highlighting functions.
4.15. The OpenShift Connector plug-in fails to deploy an application in a restricted environment
The OpenShift Connector plug-in fails to deploy because of the inability to access the
odo image in the disconnected environment.
4.16. Debug configuration missing
Debug configurations are not loaded. The Debug panel displays:
- Refresh the page, and the debug configurations appear.
4.17. Updating CodeReady Workspaces instance from multi-host to single-host strategy breaks the Create Workspace UI
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.
Re-deploy the devfile registry Pod after the update.
4.18. CodeReady Workspaces fails to resolve devfiles for Bitbucket factory for public repositories
Bitbucket factory URL fails for public repositories outside OpenShift Container Platform for CodeReady Workspaces without Bitbucket OAuth enabled.
- Add the TLS sefl-signed certificate to the CodeReady Workspaces instance, see Importing untrusted TLS certificates to CodeReady Workspaces.