Chapter 2. Known issues
This section lists known issues with Red Hat CodeReady Workspaces 1.1.0. Where available, workaround suggestions are provided.
2.1. General known issues
2.1.1. Multiple workspaces fail to run at the same time
Provided the two following conditions are met, it will not be possible to run two or more workspaces at the same time:
CodeReady Workspaces uses the
commonPersistent Volume Claim (PVC) strategy
Persistent volumes (PVs) use
ReadWriteOnce(RWO) access mode
To work around this limitation, use one of the following measures:
ReadWriteMany(RWX) access mode for PVs
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.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. Workspaces fail to start with certain configurations of StorageClass
When the StorageClass resource object in OpenShift is configured with
volumeBindingMode=WaitForFirstConsumer, CodeReady Workspaces workspaces fail to start.
To work around the issue, configure StorageClass with
2.2. Known issues on OpenShift Container Platform 4.0
2.2.1. Logging in using OpenShift OAuth does not work
On OpenShift Container Platform 4.0, 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.0, 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.