Chapter 3. Known issues

This section lists known issues with Red Hat CodeReady Workspaces 2.5. Where available, workaround suggestions are provided.

3.1. Wrong default value for a Quarkus project default folder

Instead of suggesting '/projects/' as the default target folder of the Quarkus sample project, the Create Quarkus project button of the Quarkus wizard suggests the root folder (/) instead, which is not visible from the IDE.

To work around this issue, reject the suggested destination and use /projects.

3.2. CodeReady Workspaces 2.4 Java JBoss Fuse workspaces fail to start after migration to 2.5

CodeReady Workspaces 2.4 Java JBoss Fuse workspaces deployed on OpenShift with enabled OpenShift OAuth support fail to start after updating to 2.5.

3.3. The Install dependencies command fails in PHP-DI-based workspaces

After opening php-di/console.php file in a workspace build using the PHP-DI default YAML file, the predefined command for installing dependencies fails to run.

3.4. Workspace welcome page fails to load in Single-host mode

Workspaces of the CodeReady Workspaces deployed in Single-host mode fail to load the welcome page, displaying the following error message:

Cannot GET /serverj4587ysj-jwtproxy/server-4402/webview/index.html.

3.5. Debug session for Python devfile fails to start

CodeReady Workspaces 2.5 instances do not support running a debug session for workspaces created from a Python devfile.

3.6. Manually added registries using Theia Plugin View are not reflected in the View automatically

To work around this issue, refresh the page by pressing F5 or Comd+r if using macOS.

3.7. Installing CodeReady Workspaces using crwctl server:start fails in clusters with multiple CodeReady Workspaces deployments

Installation of CodeReady Workspaces, using the crwctl server:start with OpenShift OAuth, fails or does not deploy resources if existing resources from another crwctl installation exist in the cluster.

To workaround this issue, delete old resources and perform a fresh installation. For instructions, see Installing CodeReady Workspaces on OpenShift Container Platform 3.11.

Having multiple CodeReady Workspaces deployments on the same cluster is not recommended, and the ability to do so may be removed in a future release.

3.8. Some run and build commands of the The Getting started examples may fail in the AirGap installations

Some of the sample projects included in the Getting Started devfiles are not designed for offline or airgapped use, so some commands may not work. To resolve this, user may have to talk to a organization’s administrator to get access to internal mirrors, such as NMP, Maven, and PIP.

The base functions of the Getting started ZIP-archived samples embedded in the offline devfile registry do not work.

Commands that require internet access to run: Run, Simple build `, `Outline

3.9. The workspace sharing does not work

The File > Share IDE command currently launches the Workspace tab, but the Share tab is missing.

3.10. The crwctl server:delete command breaks existing CodeReady Workspaces deployments on the same OpenShift cluster

The crwctl server:delete command removes certain cluster-scoped objects, which causes all other CodeReady Workspaces deployments to terminate unexpectedly.

To work around the issue, patch the Custom Resource Definition:

$ oc patch customresourcedefinition/checlusters.org.eclipse.che -p \
'{ "metadata": { "finalizers": null }}' --type merge

Having multiple CodeReady Workspaces deployments on the same cluster is not recommended, and the ability to do so may be removed in a future release.

3.11. Deleting a checluster custom resource causes CodeReady Workspaces Operator errors

Uninstalling the CodeReady Workspaces manually by deleting the checluster custom resource in the OperatorHub causes errors in the CodeReady Workspaces Operator. As a consequence, attempting to re-install CodeReady Workspaces in OperatorHub fails.

3.12. CodeReady Workspaces deployed without TLS support causes some features to not work properly

In CodeReady Workspaces 2.1 and later, secure HTTPS is required to use the most recent Theia IDE, and therefore TLS mode is enabled by default. Disabling the TLS support will cause user experience to suffer and some UI will not work as expected or at all.

For example, the welcome page may be blank or broken, images may be missing, and other functionality may not work properly.