Chapter 4. Known issues

On IBM Z and IBM Power, the debugging features cannot be activated in the Go workspace in OpenShift Dev Spaces 3.0. 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.

Currently, Golang-based workspaces do not include basic language server features such as code autocompletion.

OpenShift Dev Spaces might fail to create a workspace when the network is unstable. OpenShift Dev Spaces displays an error such as Failed to run the workspace: "Waiting for pod 'workspace9fbid1gnx7273d47.maven-545f8c9cf4-hw79f' was interrupted." This issue has no workaround.

Currently, the following devfiles are not supported on IBM Z and IBM Power:

This issue has no workaround.

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.

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.

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.

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

On IBM Power, the list of supported image streams is missing, which causes component creation to fail. There is currently no workaround for this issue.

Upgrading a CodeReady Workspaces 2.15 instance with the DevWorkspace engine enabled (Technology Preview) is simpler than the upgrade procedure described in the Administration Guide.

When using the Cake-php sample, the Configure Apache Web Server DocumentRoots task fails with the following error: error sed: couldn’t open temporary file /etc/httpd/conf/sedSgv1Z4: Permission denied. There is currently no workaround for this issue.

Currently, the per-workspace workspace storage strategy is not supported due to the change to the DevWorkspace engine. With migration from CodeReady Workspaces 2.15 to OpenShift Dev Spaces 3.0, existing workspaces change to the common strategy. Setting the PVC storage size other than 10 GB is currently not possible. This issue has no workaround.

Currently, users might encounter a 403 Permission Denied error when logging in to OpenShift Dev Spaces.

Workaround: Log in to OpenShift Dev Spaces in a web browser using incognito mode.

See also #21352.

In workspaces that use the default Che-Theia IDE in a proxied environment, the Workspace panel might appear blank rather than showing available commands, terminals, and applications.

Currently, you might encounter a 503 Service Unavailable or 504 Gateway Time-out error message after refreshing the page of a stopped workspace.

Workaround: Restart the workspace from the dashboard.

In CodeReady Workspaces 2.15, users were able to edit their profile information in the Account page of the dashboard. Because OpenShift OAuth is now used exclusively for user management in OpenShift Dev Spaces 3.0, users can only edit their user profile within OpenShift. The Account page in the dashboard remains for display purposes only.

When launching a sample application from the workspace, users can encounter an error message such as 502 Bad Gateway or application not available. The cause of this error is the Theia IDE displaying the notification that the application is ready before the application startup is complete.

Workaround: Wait a minute or two, and reload the browser tab.

See the related issue #21377.

Currently on IBM Power, a workspace based on the Golang sample project might create files with file permissions that prevent workspace deletion.

Currently, using the OpenShift web console, OperatorHub, to create a new OpenShift Dev Spaces instance results in the instance deployed by default in the openshift-operators namespace for Operators.

Currently, the name of the CheCluster custom resource remains the same as before upgrading from CodeReady Workspaces 2.15 to OpenShift Dev Spaces 3.0. Customers whose Checluster custom resource name is codeready-workspaces before the upgrade will find the same name after the upgrade. This issue has no workaround.

Currently, the Welcome To Your Workspace page in Che-Theia workspaces might appear blank when the workspace loads. This is caused by a missing self-signed TLS certificate in the browser.

Currently, a workspace might fail to start if an applied ConfigMap includes environment variables, env.

Users running mvnw in disconnected or restricted environments might encounter a timeout error.

Currently, Maven commands might fail for JBoss EAP XP MicroProfile and JBoss EAP 7.4 because these devfiles use two separate users and containers.

Currently, there is a known issue with the Java Gradle sample in restricted environments. Running the 1-build command to build an application might result in the FAILURE: Build failed with an exception error and failure to load a native library or not resolving a plug-in artifact in plug-in repositories. This issue has no workaround.

Currently, using the Convert button in the OpenShift Dev Spaces dashboard to convert a Deprecated Node.js workspace with the node-debug or node-debug2 plug-in fails. The following error message is displayed:

Workspace conversion failed. Failed to create a new workspace from the devfile, reason: Unable to resolve theia plugins …​.

In OpenShift Dev Spaces 3.0, the node-debug and node-debug2 plug-ins have been updated to js-debug.

Currently, workspaces with Red Hat Fuse devfile v1 fail to start after conversion to devfile v2 by clicking the Convert button in the OpenShift Dev Spaces dashboard.

Currently, workspaces might fail to start in environments using a proxy. This failure happens if you attempted to customize proxy settings by configuring the DevWorkspaceOperatorConfig custom resource and a component was restarted after that. In that case, the workspace fails to start while the Progress tab shows Waiting for workspace to start.

Currently, when an OpenShift OAuth session expires, the dashboard page appears blank.

Currently, OpenShift Dev Spaces fails to start new workspaces with a clone of a GitHub-hosted repository when using the #https://github.com/<user_or_org>/<repository>/pull/<pull_request_id> URL syntax. The workspace-starting page displays the following error message: Failed to resolve a devfile. Failed to request factory resolver: Internal Server Error occurred.

Currently, a workspace might fail to start, and then you might be unable to delete it. This is caused by a persistent volume claim (PVC) issue. Subsequently, the same problem occurs with other workspaces.

Currently, starting a workspace that uses the Technology Preview Visual Studio Code on OpenShift with a self-signed TLS certificate results in a blank browser tab.

Currently, deploying the Vert.x Health Check Example application by running the 6-deploy-to-openshift command fails in disconnected environments. There is currently no workaround for this issue.

Currently, under certain conditions, such as OLM restart or cluster upgrade, the Dev Spaces Operator for OpenShift Dev Spaces 3.0.0 might automatically install the DevWorkspace Operator even if it is already present on the cluster. This might cause severe consequences: the OpenShift web terminal might stop working, or the DevWorkspace Operator admission webhooks might not work properly, which might affect the behavior of the cluster.

You can detect this issue on your cluster by checking Installed Operators in the OpenShift web console: if this problem is occurring, you see multiple entries for the DevWorkspace Operator or one entry that is stuck in a loop of Replacing and Pending.