Red Hat SummitThis documentation is for a release that is no longer maintained
See documentation for the latest supported version.Chapter 7. Known issues
7.1. Workspaces using ubi9-based image with no libbrotli library as a tools container can not start
There is a known issue affecting workspaces that use a ubi-9-based image without libbrotli library as a tools container. If you start the workspace, the following error message appears: "Failed to open the workspace: The workspace status remains "Starting" in the last 300 seconds."
The time listed in the error message can vary.
Workaround
-
Use another ubi9-based image with
libbrotlilibrary, e.g. quay.io/devfile/universal-developer-image:ubi9-latest. -
Rebuild your custom ubi9-based image to include
libbrotlilibrary.
Additional resources
7.2. Git user.name and user.email not set up automatically
There is a known issue affecting the automatic setup of Git user.name and user.email in the `gitconfig file after you configured your access token (PAT) or OAuth. If you open User Dashboard > Gitconfig page after PAT or OAuth configuration, you receive the following error message: "Author identity unknown." A workaround exists.
Workaround
-
Add git
user.nameanduser.email.manually in User Preferences > Gitconfig page.
Additional resources
7.3. Outdated Visual Studio Code - Open Source ("CODE - OSS") appears in workspaces created in previous Dev Spaces version
There is a known issue affecting Visual Studio Code - Open Source ("CODE - OSS") after you upgrade Dev Spaces from version 3.17.0 to 3.18.0. If you open a workspace previously created from a sample in Dev Spaces 3.17.0, an old version (1.93.0) of Visual Studio Code appears in it instead of the new version (1.96.0).
There is currently no workaround available.
Additional resources
7.4. 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
7.5. FIPS compliance update
There’s a known issue with FIPS compliance that results in certain cryptographic modules not being FIPS-validated. Below is a list of requirements and limitations for using FIPS with OpenShift Dev Spaces:
Required cluster and operator updates
Update your Red Hat OpenShift Container Platform installation to the latest z-stream update for 4.14, 4.15, 4.16, or 4.17 as appropriate. If you do not already have FIPS enabled, you will need to uninstall and reinstall.
Once the cluster is up and running, install OpenShift Dev Spaces 3.18 (3.18-36) and verify that the latest DevWorkspace operator bundle 0.32 (0.32-2) or newer is also installed and updated. See https://catalog.redhat.com/software/containers/devworkspace/devworkspace-operator-bundle/60ec9f48744684587e2186a3
Golang compiler in UDI image
The Universal Developer Image (UDI) container includes a golang compiler, which was built without the CGO_ENABLED=1 flag. The check-payload scanner ( https://github.com/openshift/check-payload ) will throw an error, but this can be safely ignored provided that anything you build with this compiler sets the correct flag CGO_ENABLED=1 and does NOT use extldflags -static or -tags no_openssl.
The resulting binaries can be scanned and should pass without error.
Statically linked binaries
You can find statically linked binaries not related to cryptography in these two containers:
- code-rhel8
- idea-rhel8.
As they are not related to cryptography, they do not affect FIPS compliance.
Helm support for FIPS
The UDI and Code containers includes the helm binary, which was not compiled with FIPS support. If you are in a FIPS environment do not use helm.
Kubedock support for FIPS
The UDI container includes the kubedock binary, which was not compiled with FIPS support. If you are in a FIPS environment do not use kubedock.
Additional resources
7.6. Debugger does not work in the .NET sample
Currently, the debugger in Microsoft Visual Studio Code - Open Source does not work in the .NET sample.
Workaround
Use a different image from the following sources:
Additional resources
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}