Known issues
The following release notes detail the known issues for the Red Hat OpenShift Dev Spaces 3.30 general availability release.
SSH development workflow fails when connecting to UBI 9-based workspaces
There is a known issue where connecting to Dev Spaces workspaces from local IDEs using SSH fails when the workspace is based on UBI 9 images. This affects remote development workflows where you use your local IDE to edit and debug code running in a cloud-based workspace. The connection fails with authentication or protocol errors.
Workaround: Update your workspace to use the latest UBI 9 base images, which include the fixed SSH server package. To apply the fix:
- Update your devfile to reference the latest UBI 9 base image
- Restart your workspace to apply the updated base image
- Reconnect from your local IDE using SSH
Additional resources
The C# extension is not available for .NET workspaces on IBM Power and IBM Z
There is a known issue where the recommended C# extension (muhammad-sammy.csharp) is not available in .NET sample workspaces on IBM Power (ppc64le) and IBM Z (s390x).
Workaround: To work around this issue, install version 2.110.4 of the muhammad-sammy.csharp extension manually from Content from open-vsx.org is not included.open-vsx.org.
Alternatively, patch the CheCluster custom resource to use the embedded plugin registry image from the previous release: registry.redhat.io/devspaces/pluginregistry-rhel9:3.27.1
Additional resources
Podman build fails with a permission denied error on IBM Z with NFS storage
There is a known issue where container builds using Podman fail with a permission denied error in workspaces on IBM Z (s390x) that use NFS or network-attached storage classes.
Workaround: Redirect the Podman storage directories to a local path by creating or editing the ~/.config/containers/storage.conf file in the workspace:
[storage]
driver = "vfs"
graphroot = "/tmp/user-containers/storage"
runroot = "/tmp/user-containers/run"Additional resources
Workspaces using JetBrains Toolbox App (desktop) editor ignore idling timeouts
There is a known issue with the desktop version of the JetBrains Toolbox App editor. Workspaces using this editor ignore idling timeouts specified by CheCluster properties such as secondsOfRunBeforeIdling and secondsOfInactivityBeforeIdling. There is currently no workaround available.
Additional resources
SSH connection to workspaces fails when nested containers are enabled
There is a known issue where SSH connections to developer workspaces fail when the disableContainerRunCapabilities option is set to false in the CheCluster custom resource. This affects the Visual Studio Code (desktop) and JetBrains remote workflows that connect over SSH. The SSH daemon logs the following error:
cannot write into audit linux_audit_write_entry failed: Permission denied
Workaround: Set disableContainerRunCapabilities to true in the CheCluster custom resource to disable the container run capabilities. SSH connections to workspaces function correctly with this setting.
Additional resources
Workspaces using Visual Studio Code (desktop) editor ignores idling timeouts
There is a known issue with the desktop version of Visual Studio Code editor. Workspaces using these editor ignore idling timeouts specified by CheCluster properties such as secondsOfRunBeforeIdling and secondsOfInactivityBeforeIdling. There is currently no workaround available.
Additional resources
"504 Gateway Time-out" error
There is a known issue affecting the use of IntelliJ IDEA Ultimate IDE on the arm64 architecture. When you start a workspace in the IDE, the following error message appears: "504 Gateway Time-out". There is no workaround available.
Additional resources
"PostStartHook failed" error
There is a known issue with using the Ansible sample on the arm64 architecture. The Ansible sample fails to start and the following error message appears: "Error creating DevWorkspace deployment: Detected unrecoverable event FailedPostStartHook: PostStartHook failed." There is no workaround available.
Additional resources
.NET sample fails to start on arm64 architecture
There is a known issue where the .NET sample fails to start on the arm64 architecture because there is no quay.io/devspaces/dotnet-90 image available for arm64. There is no workaround available.
Additional resources
Error when starting a workspace in Dev Spaces deployed to OpenShift Platform 4.18
There is a known issue affecting workspaces in Dev Spaces deployed to OpenShift Platform 4.18. When you start the workspace, the following error message appears: "Error creating DevWorkspace deployment: Container tools has state ImagePullBackOff".
- Restart the workspace.
Additional resources
JetBrains editors cause workspace startup failure on IBM Power and IBM Z
There is currently a known issue affecting the use of the desktop versions of JetBrains IDEs with IBM Power, and IBM Z architectures. The downloaded JetBrains IDE binaries are not multi-arch, causing workspace startup to fail. There is currently no workaround available.
Additional resources
Refresh token mode causes cyclic reload of the workspace start page
There is a known issue when experimental refresh token mode is applied using the CHE_FORCE_REFRESH_PERSONAL_ACCESS_TOKEN property for the GitHub and Microsoft Azure DevOps OAuth providers. This causes the workspace starts to reload the dashboard cyclically, creating a new personal access token on each page restart. The refresh token mode works correctly for 'GitLab' and 'BitBucket' OAuth providers.
Additional resources