Chapter 2. Known issues

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

2.1. General known issues

2.1.1. Multiple workspaces fail to run at the same time

The following two conditions prevent the user from running multiple workspaces simultaneously:

  • CodeReady Workspaces uses the common Persistent Volume Claim (PVC) strategy
  • Persistent volumes (PVs) use ReadWriteOnce (RWO) access mode

To work around this limitation to run multiple workspaces simultaneously, use one of the following measures:

  • set ReadWriteMany (RWX) access mode for PVs
  • use the unique PVC strategy
  • use the per-workspace strategy

2.1.2. Undefined error when starting a workspace

When starting workspace a broken websocket connection can cause an Undefined error. The error does not impact the workspace start process, and refreshing the browser page fixes it.

2.1.3. "Authorization token is missed" error at the login page

After installing CodeReady Workspaces on OpenShift Container Platform with TLS support and a self-signed certificate, it is not possible to enter the login page, and the Authorization token is missed. Click here to reload page error message is displayed.

To work around this limitation, add the self-signed TLS certificates to the browser for each route exposed in CodeReady Workspaces. This includes the codeready-workspaces deployment, the keycloak (Red Hat Single Sign-On) deployment, the plugin-registry and devfile-registry deployments, and any other ones you might create thereafter. Repeat this for all browsers you use to access CodeReady Workspaces.

For instructions on adding self-signed certificates, follow the documentation for your browser.

2.1.4. Occasional NullPointerException when opening a workspace from the "Java 1.8" stack with an imported Java project

When opening a workspace (Java 1.8 stack) with an imported Java project, an error (NullPointerException) is encountered. The project does not open. To work around this issue, open the project again.

2.1.5. Delay when launching commands using the command palette

When launching a command using the command palette, a delay of approximately five seconds occurs before the real execution of the command.

To work around this issue, activate the JDT.LS (Java Language Server Protocol) installer in workspace configuration in Dashboard > Workspace details page.

2.1.6. New terminal windows freeze after a minute of inactivity on macOS X

When a new terminal is opened and the user stops typing, the terminal becomes unresponsive after some time of inactivity. The user must close the terminal and open a new one to continue.

2.1.7. Workspaces fail to start with certain configurations of StorageClass

When the StorageClass resource object in OpenShift is configured with volumeBindingMode=WaitForFirstConsumer, the workspaces in CodeReady Workspaces fail to start.

To work around the issue, take the following steps:

  1. In the OpenShift web console, expand Workloads and click Config Maps > custom.
  2. Click the YAML tab.
  3. In the data section, add the following environment variable and set it to false:


    The CHE_INFRA_KUBERNETES_PVC_WAIT__BOUND environment variable is used to disable or enable the wait time for the PVCs to bind.

  4. Save the YAML file.
  5. Run the following commands to manually scale down and then scale up the deployment to ensure that the wait time for PVCs to bind is disabled:

    $ oc scale deployment/codeready --replicas=0
    $ oc scale deployment/codeready --replicas=1

2.2. Known issues on OpenShift Container Platform 4.1

2.2.1. Logging in using OpenShift OAuth does not work

On OpenShift Container Platform 4.1, authentication with Red Hat SSO that is configured to use OpenShift OAuth does not work. There is no work around for this issue other than not using OpenShift OAuth.

2.2.2. Error marker fails to appear in Java-stack workspaces

On OpenShift Container Platform 4.1, when editing Java source code in a CodeReady Workspaces workspace based on the Java stack, error markers do not appear when expected. At times, an error marker appears when there should be none. Reloading the page solves the issue only temporarily.

2.2.3. CodeReady Workspaces scalability workaround on OCP 4.1/AWS

For details, see CodeReady Workspaces scalability workaround on OCP 4.1/AWS.