Chapter 4. Known issues
4.1. Debugging cannot be activated in Go workspaces on IBM Z and IBM Power Systems
On IBM Z and IBM Power Systems, the debugging features cannot be activated in the Go workspace in CodeReady Workspaces 2.11. 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.
4.2. Language server features are not preinstalled in Go workspaces
Golang based workspaces do not include basic language server features such as code autocompletion.
- Run the CodeReady Workspaces instance in a non-restricted environment.
- Install the required module by using the Install button in the IDE dialog box.
4.3. Misleading error message for a workspace failure caused by the
mkdir Pod timeout
Lack of OpenShift Container Platform cluster resources are causing a failure accompanied by the following, misleading error message: Your session has expired. Please, log in to CodeReady Workspaces again to get access to your OpenShift account.
- Provide more resources to the OpenShift Container Platform cluster.
4.4. Starting multiple instances of the same task fails
Currently, when you start a task from My workspace multiple times, the task does not end. The IDE displays the loading circle but no check mark (✓). As a result, the IDE cannot start the following task.
- Execute a task in the My workspace environment only once.
4.5. Error starting a PHP debug session
Currently, CodeReady Workspaces fails to run a PHP debug session with the following error message: There was an error starting the debug session, check the logs for more details. PHP is a Technology Preview feature. There is currently no workaround for this issue.
4.6. Attempts to clone a workspace from a Quick Add sample result in an error under the
Currently, there is a known issue related to 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.
crwctl binaries are not supported on IBM Z and IBM Power Systems
crwctl binaries do not run on IBM Z and IBM Power Systems. These platforms are available uniquely as targets onto which to deploy CodeReady Workspaces.
crwctlfrom a supported platform.
4.8. Workspace creation fails on unstable networks
CodeReady Workspaces is intermittently failing 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.
4.9. Unsupported devfiles on IBM Z and IBM Power Systems
Currently, the following devfiles are not supported on IBM Z and IBM Power Systems:
- EAP for OpenJDK 8
- Apache Camel K by Red Hat
- Do not use unsupported languages on IBM Z and IBM Power Systems.
4.10. 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.11. Error message asking the user to log in again at workspace startup
Currently, the user may receive the following error during workspace startup: Your session has expired. Please login to Che again to get access to your OpenShift account.
- Log in again.
4.12. No delegateCommandHandler error for Java with the JBoss EAP 7.3 devfile
Currently, 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 currently no workaround for this issue.
4.13. No display for a task after a networking issue
Currently, 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 currently no workaround for this issue.
4.14. The OpenShift Connector plug-in fails to deploy an application in a restricted environment
Currently, the OpenShift Connector plug-in fails to deploy because of the inability to access the
odo image in the disconnected environment. There is currently no workaround for this issue.
4.15. The DEBUG configuration is missing
Currently, the DEBUG panel displays No Configurations in the drop-down list because no configurations are loaded.
- Refresh the page to display the debug configurations.
4.16. Updating the CodeReady Workspaces instance from the multi-host to the single-host strategy breaks the Create Workspace UI
Currently, after patching the CodeReady Workspaces 2.11 instance from
single-host, the Dashboard Create Workspace page displays an incomplete UI with missing icons.
- Re-deploy the devfile registry Pod after the update.
4.17. The Python workspace displays the "Python not installed" error message
Currently, the Python workspace displays unexpected dialog boxes, including the following error: Python is not installed. Please download and install Python before using the extension. There is currently no workaround for this issue.
4.18. Java analytic plug-in fails in the
Java with JBoss EAP XP 3.0 MicroProfile sample
The Java analytic plugin doesn’t work with the
jboss-eap-quickstart sample project, used by the
JBoss EAP XP 3.0 MicroProfile devfile.
4.19. Workspace creation fails after upgrading DevWorkspace
Currently, after upgrading DevWorkspace 2.10.1 to 2.11, CodeReady Workspaces fails to create a workspace with the following error: Getting workspace detail data failed. Failed to fetch the workspace <workspace_name>, reason: Could not get exposed endpoints for DevWorkspace: controller not ready to resolve the workspace routing.
Execute the following commands:
oc delete chemanager -n devworkspace-che --wait
oc delete namespace devworkspace-che
4.20. Namespace restriction for OpenShift Dedicated and ROSA
Currently, CodeReady Workspaces must not be deployed to the
openshift-workspaces namespace on OpenShift Dedicated and ROSA.
- Use another namespace when deploying CodeReady Workspaces on OpenShift Dedicated and ROSA.
4.21. Technology preview for deploying CodeReady Workspaces 2.11 with the Dev Workspace engine
Support for deploying CodeReady Workspaces 2.11 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 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.
- Workspaces are not protected from inner OpenShift cluster access.
- When deploying CodeReady Workspaces in a restricted environment, starting workspaces will fail because proxy and untrusted TLS certificates are not supported.
- The volumes needed for plug-ins need to be declared in the workspace devfile.
- Workspaces idling is not supported.
- GitHub, GitLab, Bitbucket OAuth flow to automatically configure users accounts is not supported.
- Clusters with a network policy that isolates namespaces networks are not supported.
- Asynchronous storage mode for workspaces is not supported.
- Selecting the editor from the dashboard is not supported.
4.22. Upstream sample devfiles are not supported
Upstream sample devfiles are designed for Eclipse Che. CodeReady Workspaces doesn’t support these samples. A workspace running with the Dev Workspace engine may fail to start when using an upstream sample devfile.
- Use supported Red Hat CodeReady Workspaces sample devfiles.
4.23. The OpenShift Connector plug-in does not allow the creation of a new component on IBM Power Systems
On IBM Power Systems, the list of supported image streams is missing, which causes component creation to fail.
4.24. Uninstalling CodeReady Workspaces fails when the Kubernetes Image Puller is installed
When the Kubernetes Image Puller is installed, uninstalling CodeReady Workspaces fails.
- The deletion process doesn’t remove the Kubernetes Image Puller finalizer.
CheClusterCustom Resource is not empty and can’t be removed.
- Disable the Kubernetes Image Puller before uninstalling CodeReady Workspaces.