Chapter 4. Known issues
Chapter 4. Known issues 4.1. Debugging cannot be activated in Go workspaces on IBM Z and IBM Power On IBM Z and IBM Power, the debugging features cannot be activated in the Go workspace in CodeReady Workspaces 2.15. 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. Additional resources CRW-1349 4.2. Language server features are not preinstalled in Go workspaces Golang based workspaces do not include basic language server features such as code autocompletion. Workaround Run the CodeReady Workspaces instance in a non-restricted environment. Install the required module by using the Install button in the IDE dialog box. Additional resources CRW-1521 4.3. Attempts to clone a workspace from a Quick Add sample result in an error under the single-host strategy When using the single-host strategy for workspace exposure, attempting to clone a workspace from a Quick Add sample results in an error. There is currently no workaround for this issue. Additional resources CRW-1851 4.4. Workspace creation fails on unstable networks CodeReady Workspaces might fail to create a workspace when the network is unstable. CodeReady Workspaces displays an error such as the following: Failed to run the workspace: "Waiting for pod 'workspace9fbid1gnx7273d47.maven-545f8c9cf4-hw79f' was interrupted." This issue has no workaround. Additional resources CRW-1888 4.5. Unsupported devfiles on IBM Z and IBM Power The following devfiles are not supported on IBM Z and IBM Power: EAP for OpenJDK 8 .Net Fuse Apache Camel K by Red Hat Workaround Do not use unsupported languages on IBM Z and IBM Power. Additional resources CRW-1896 4.6. No delegateCommandHandler error for Java with the JBoss EAP 7.3 devfile 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. Additional resources CRW-2067 4.7. No display for a task after a networking 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. Additional resources CRW-2070 4.8. The OpenShift Connector plug-in fails to deploy an application in a restricted environment 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. Additional resources CRW-2071 4.9. The DEBUG configuration is missing The DEBUG panel displays No Configurations in the drop-down list because no configurations are loaded. Workaround Refresh the page to display the debug configurations. Additional resources CRW-2078 4.10. Namespace restriction for OpenShift Dedicated and ROSA Currently, there is a restriction for OpenShift Dedicated and ROSA: CodeReady Workspaces must not be deployed to the openshift-workspaces namespace. Workaround Use another namespace when deploying CodeReady Workspaces on OpenShift Dedicated and ROSA. Additional resources CRW-2235 4.11. The OpenShift Connector plug-in does not allow the creation of a new component on IBM Power 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. Additional resources CRW-2255 4.12. Upgrading a CodeReady Workspaces instance with the Dev Workspace engine enabled requires manual steps Currently, upgrading a CodeReady Workspaces instance with the Dev Workspace engine enabled requires the following manual steps as a workaround: Workaround Unsubscribe the CodeReady Workspaces Operator from the latest channel. Remove the Dev Workspace Controller namespace. Subscribe the CodeReady Workspaces Operator to the tech-preview-latest-all-namespaces channel. Support for deploying CodeReady Workspaces 2.15 with the Dev Workspace engine is available as a Technology Preview feature for OpenShift Container Platform 4.8. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not fully function. Red Hat does not suggest using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. Additional resources CRW-2357 4.13. The Image Puller does not work with the tech-preview-latest-all-namespaces channel Currently, when using OperatorHub to install CodeReady Workspaces with the Dev Workspace engine, you cannot enable the Image Puller. The Image Puller currently does not work with the tech-preview-latest-all-namespaces channel. Workaround Fetch the standalone CodeReady Workspaces imagepuller-rhel8 image and use it manually to perform image pulls across the cluster. Additional resources CRW-2441 4.14. The command Configure Apache Web Server DocumentRoot does not work in the Cake-php sample project on IBM Power When using the Cake-php sample, the Configure Apache Web Server DocumentRoots task fails with the following error: There is currently no workaround for this issue. Additional resources CRW-2452 4.15. Empty page after the user session expires Currently, a CodeReady Workspaces instance might display an empty page after the user session expires. There is currently no workaround for this issue. Additional resources CRW-2690 4.16. Empty dashboard after a server error Currently, the dashboard of a CodeReady Workspaces instance might display an empty page after a server error. There is currently no workaround for this issue. Additional resources CRW-2727
error sed: couldn't open temporary file /etc/httpd/conf/sedSgv1Z4: Permission denied