-
Language:
English
-
Language:
English
Release Notes and Known Issues
Release Notes and Known Issues for Red Hat CodeReady Workspaces 1.1.0
Robert Kratky
rkratky@redhat.com
devtools-docs@redhat.com
Abstract
Chapter 1. Release notes
Red Hat CodeReady Workspaces is a next-generation web-based integrated development environment (IDE). CodeReady Workspaces runs in OpenShift and is well-suited for container-based development.
This section documents the most important features and bug fixes in the Red Hat CodeReady Workspaces product.
1.1. About Red Hat CodeReady Workspaces
Red Hat CodeReady Workspaces 1.1 provides cloud developer workspace server and browser-based IDE built for teams and organizations. CodeReady Workspaces includes ready-to-use developer stacks for most of the popular programming languages, frameworks, and Red Hat technologies.
Built on Eclipse Che (version 6.18.2), the next-generation IDE and most advanced open-source cloud development environment, CodeReady Workspaces provides developer workspaces, which includes all the tools and the dependencies that are needed to code, build, test, run, and debug applications. The entire product runs in the cloud and eliminates the need to install anything on a local machine.
CodeReady Workspaces offers:
- fast onboarding capabilities for teams with powerful collaboration, workspace automation, and management at scale
- removes inconsistencies and the “works on my machine” syndrome
- protects source code from the hard-to-secure developer and personal laptops
CodeReady Workspaces 1.1 introduces:
- Compatibility with OpenShift 4.0
- Installation in disconnected environments
- Simplified configuration of OpenShift OAuth and cluster certificates
Red Hat CodeReady Workspaces 1.1 is available today in the Red Hat Container Catalog. Install it on OpenShift Container Platform, starting at version 3.11 (or request to have it deployed on OpenShift Dedicated), by following the instructions in the Administration Guide.
For OpenShift 4.0, CodeReady Workspaces 1.1 is available today in Developer Preview from the Operator Hub. Based on a new operator that leverages the Operator Lifecycle Manager (OLM), the installation flow is getting simpler and can be handled without leaving the OpenShift Console. The OLM also allows for automated updates. If you already have OpenShift 4.0, follow the dedicated documentation: Installing CodeReady Workspaces from Operator Hub.
1.1.1. Installing and deploying CodeReady Workspaces
For OpenShift 3.11, see the Installing CodeReady Workspaces chapter of the Administration Guide.
For OpenShift 4.0, see the Installing CodeReady Workspaces from Operator Hub chapter of the Administration Guide.
1.1.2. Support policy
For Red Hat CodeReady Workspaces 1.1.0, Red Hat will provide support for deployment, configuration, and use of the product.
CodeReady Workspaces 1.1.0 has been tested on Chrome version 71.0.3578.98 (Official Build) (64-bit).
For more information, see CodeReady Workspaces life-cycle and support policy.
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
common
Persistent Volume Claim (PVC) strategy -
Persistent volumes (PVs) use
ReadWriteOnce
(RWO) access mode
To work around this limitation, 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 certificate to the 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. 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 volumeBindingMode=Immediate
.
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.