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

Additional resources

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.

Workaround

  1. Run the CodeReady Workspaces instance in a non-restricted environment.
  2. Install the required module by using the Install button in the IDE dialog box.

Additional resources

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

A lack of OpenShift Container Platform cluster resources causes a failure. This failure causes a misleading message: Your session has expired. Please, log in to CodeReady Workspaces again to get access to your OpenShift account.

Workaround

  • Provide more resources to the OpenShift Container Platform cluster.

Additional resources

4.4. Attempts to clone a workspace from a Quick Add sample result in an error under the single-host strategy

When using 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.

Additional resources

4.5. crwctl binaries are not supported on IBM Z and IBM Power Systems

The crwctl binaries do not run on IBM Z and IBM Power Systems. These platforms are available as targets for deploying CodeReady Workspaces.

Workaround

  • Run crwctl from a supported platform.

Additional resources

4.6. Workspace creation fails on unstable networks

CodeReady Workspaces might fail 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.

Additional resources

4.7. Unsupported devfiles on IBM Z and IBM Power Systems

The following devfiles are not supported on IBM Z and IBM Power Systems:

  • EAP for OpenJDK 8
  • .Net
  • Fuse
  • Apache Camel K by Red Hat

Workaround

  • Do not use unsupported languages on IBM Z and IBM Power Systems.

Additional resources

4.8. 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 fully function. 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.9. Error message asking the user to log in again at workspace startup

When starting a workspace, users might receive the following error message: Your session has expired. Please login to Che again to get access to your OpenShift account.

Workaround

  • Log in again.

Additional resources

4.10. No delegateCommandHandler error for Java with the JBoss EAP 7.3 devfile

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 no workaround for this issue.

Additional resources

4.11. No display for a task after a networking issue

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 no workaround for this issue.

Additional resources

4.12. 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. There is no workaround for this issue.

Additional resources

4.13. The DEBUG configuration is missing

The DEBUG panel displays No Configurations in the drop-down list because no configurations are loaded.

Workaround

  • Refresh the page to display the debug configurations.

Additional resources

4.14. Updating the CodeReady Workspaces instance from the multi-host to the single-host strategy breaks the Create Workspace UI

After patching the CodeReady Workspaces 2.12 instance from multi-host to single-host, the Dashboard Create Workspace page displays an incomplete UI with missing icons.

Workaround

  • Re-deploy the devfile registry Pod after the update.

Additional resources

4.15. Namespace restriction for OpenShift Dedicated and ROSA

Don’t deploy CodeReady Workspaces to the openshift-workspaces namespace on OpenShift Dedicated and ROSA.

Workaround

  • Use another namespace when deploying CodeReady Workspaces on OpenShift Dedicated and ROSA.

Additional resources

4.16. 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 might fail to start when using an upstream sample devfile.

Workaround

  • Use supported Red Hat CodeReady Workspaces sample devfiles.

Additional resources

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

Additional resources

4.18. Uninstalling CodeReady Workspaces fails when the Kubernetes Image Puller is installed

When the Kubernetes Image Puller is installed, uninstalling CodeReady Workspaces fails, meaning:

  • The deletion process doesn’t remove the Kubernetes Image Puller finalizer.
  • The CheCluster Custom Resource is not empty and can’t be removed.

Workaround

  • Disable the Kubernetes Image Puller before uninstalling CodeReady Workspaces.

Additional resources

4.19. Technology preview for deploying CodeReady Workspaces 2.12 with the Dev Workspace engine

Support for deploying CodeReady Workspaces 2.12 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 fully function. 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.

Known limitations

  • 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.
  • 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.
  • Upgrading an instance with the Dev Workspace engine enabled requires manual steps.

Additional resources

4.20. Clone from GitHub using the IDE UI fails

The Git: Clone IDE command does not work.

Workaround

  • Use the git CLI to clone the repository.

Additional resources

4.21. Prometheus doesn’t display metrics when using the tech-preview Operator channel

After deploying the CodeReady Workspaces Operator form the tech-preview Operator channel in the default namespace and creating a CheCluster Custom Resource in the default namespace, the OpenShift Prometheus UI doesn’t display the metrics.

Workaround

  • Use the latest Operator channel.

Additional resources

4.22. The OpenShift Container Platform console displays confusing names in the backup related tabs

The OpenShift Container Platform console displays confusing names in the backup related tabs. CheBackupServerConfigurations appears rather than the expected name: CodeReady Workspaces instance Specification, CodeReady Workspaces Backup Server, CodeReady Workspaces Backup Specification or CodeReady Workspaces Restore Specification . This issue has no workaround.

Additional resources

4.23. Upgrading an instance with the Dev Workspace engine enabled requires manual steps

Upgrading an instance with the Dev Workspace engine enabled requires manual steps.

Support for deploying CodeReady Workspaces 2.12 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 fully function. 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.

Procedure

  1. Unsubscribe the CodeReady Workspaces Operator from the latest channel.
  2. Remove the Dev Workspace Controller namespace.
  3. Subscribe the CodeReady Workspaces Operator to the tech-preview-latest-all-namespaces channel.

Additional resources

4.24. keycloak and codeready pods do not restart automatically after adding a ConfigMap

After adding a ConfigMap to a CodeReady Workspaces instance, the keycloak and codeready Pods do not restart automatically.

Workaround

  • Manually restart the keycloak and codeready pods after adding a ConfigMap.

Additional resources

4.25. Uninstalling CodeReady Workspaces fails when the Dev Workspace engine is enabled

When the Dev Workspace engine is enabled, uninstalling CodeReady Workspaces fails, meaning:

  • The deletion process doesn’t remove the Dev Workspace engine.

Workaround

  • In the openshift-operators namespace:

    1. Uninstall the CodeReady Workspaces and Dev Workspace Operators
    2. Delete the controller.devfile.io WebHooks.
    3. Delete the devworkspace-webhook-server Deployment.
    4. Delete the `devworkspace-webhookserver" Service.
    5. Delete all **.devfile.io and **.org.eclipse.che ConfigMaps.
    6. Delete all devworkspace-** Secrets.

Additional resources