Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 7. Known issues

7.1. Microsoft Visual Studio Code - Open Source extensions not automatically installed

There is a known issue where automatic installation of the recommended Microsoft Visual Studio Code - Open Source extensions fails if you’re using a Java or Ansible sample.

Workaround

  • Refresh the workspace tab in the browser.

Additional resources

7.2. 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.11, 4.12, or 4.13 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.7.1 (3.7-264) and verify that the latest DevWorkspace operator bundle 0.21.2 (0.21-7) 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 container includes the helm binary, which was not compiled with FIPS support. If you are in a FIPS environment do not use helm.

Additional resources

7.3. Incorrect user name and email in commit messages for some users

There is currently a known issue for users who are using a Kubernetes Secret with their Git-provider credentials. The user name and email for Git operations in workspaces for those users are currently taken from the user-profile Secret of the <user>-devspaces namespace.

Important

Workaround

  • In the editor terminal of the running workspace, run the following commands to set your commit author name and email: 

    git commit config --global user.name <your_name>
git commit config --global user.email <your_email>
    Copy to Clipboard

Additional resources

7.4. 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

Additional resources

Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat