Known issues

You can find the known issues that are identified in this version of HCL DevOps Loop.

Known issues in DevOps Loop 2026.08 (2.0.2.1)

The following known issue is identified in this release:

ID Description
NEXUS00006751 When you create a teamspace by using an email ID that is exactly 12 characters long, the operation might fail at the Measure phase because the MongoDB 5.9.2 package incorrectly treats the email value as an ObjectId. In this case, the teamspace might be created in Velocity, but the overall teamspace creation task does not complete successfully.

To work around this problem, you must avoid using email IDs that are exactly 12 characters long.
NEXUS00006817 When you run tests through Deploy in an HCL DevOps Loop in an air-gapped environment, the tests might fail because the HCL DevOps Test Hub plugin version 4.3 does not work correctly with the Test Hub integration.

To work around this problem, navigate to Deploy and update the HCL DevOps Test Hub plugin to version 5.0 to run Test Hub tests successfully.

Known issues from earlier versions

The known issues identified in the earlier versions of DevOps Loop that are still applicable are as follows:

ID Description Identified in version Resolved in version
NEXUS00006323

When you install IBM DevOps Loop version 2.0.2 by using the default IBM entitled registry, DevOps Code dev containers that use the GitHub Copilot extension image or Trivy images might fail to start because the image registry is not configured correctly for the generated image specification.

To work around this problem, you must update the IMAGE_REGISTRY environment variable in the devops-code-container-mgr deployment after the installation is complete by following these steps:
  1. From a workstation where the Kubernetes cluster is configured and the kubectl command is available, run the following command:
    kubectl edit deployment devops-code-container-mgr -n devops-loop
  2. In the image deployment configuration, update the IMAGE_REGISTRY environment variable value with the following:
    env:
- name: IMAGE_REGISTRY
  value: cp.icr.io/cp
  3. Save the changes and exit the editor that opened when you ran the kubectl edit command.

    Kubernetes restarts the devops-code-container-mgr pod after the deployment configuration is updated.

After the pod restrarts, you can create DevOps Code dev containers by using the GitHub Copilot extension image and Trivy images successfully. If you run the DevOps Loop installation script again, you must repeat this configuration change.

Alternatively, before rerunning the installation, you must update the ibm-devops-loop/charts/ibm-devopscode/templates/helper-deployment.yaml template to set the IMAGE_REGISTRY value correctly.

 2.0.2 2.0.2.1
NEXUS00006321

The demo installation scripts that are included with DevOps Loop 2.0.2 contain incorrect configuration values. As a result, the scripts might fail or produce unexpected results unless they are corrected before execution.

To work around this problem, you must make the following changes before running the demo installation scripts:
  1. Update the Loop chart version to the correct value:
    LOOP_CHART_VERSION=2.0.200
  2. Correct the JSONPath command by removing the extra closing brace ()).
    Replace: 
    -o jsonpath="{.data.valkey-password}" | base64 -d)
    with 
    -o jsonpath="{.data.valkey-password}" | base64 -d

    After making these changes, you must rerun the demo installation scripts.

 2.0.2 2.0.2.1
NEXUS00005995 When you upgrade the DevOps Loop platform to version 2.0.2, existing 2.0.1 Learning Loops continue to use the Ecological Payments sample application and do not include the new Loop Genie tasks that are introduced in version 2.0.2. The Upgrade Loop option is not available for loops that were created in version 2.0.1.

To work around this problem, you must create a new Learning Loop after upgrading to DevOps Loop 2.0.2 to use the CycleShop sample application and the latest Loop Genie tasks and tools.

 2.0.2
NEXUS00006310 When teamspace creation fails, and you select Cancel and Retry Later, the failed teamspace is expected to appear in a red ribbon for later retry. Instead, the page becomes unresponsive.

To work around this problem, you must sign in with a different user account and create the Teamspace again.

 2.0.2 2.0.2.1
NEXUS00006264

When you use Loop Genie to list the available loops, the request might fail because of a tool or domain metadata validation issue. As a result, Loop Genie might not display the available loops.

Currently, there is no workaround for this problem.

 2.0.2
NEXUS00006216

When you use Loop Genie, the first request in a new session might fail with an internal server error because of API rate limiting. Although model validation completes successfully, the initial request might not be processed.

To work around this problem, you must retry the request after a short interval. If the problem persists, you must start a new Loop Genie session and try the request again.

 2.0.2
NEXUS00006225 When you use Loop Genie in a long chat session, the conversation context might not be summarized correctly as the model context window approaches its limit. As a result, Loop Genie might not respond as expected or stop processing requests.

To work around this problem, you must start a new Loop Genie session and continue your conversation there.

 2.0.2
NEXUS00005427 When a user is assigned an unsupported Keycloak group and Measure/Release role combination, the system does not display a clear authorization error. Instead, the user might experience one of the following behaviors:

  • Repeated login redirect/loop during authentication

  • Inability to load Measure or Release pages

  • No explicit error message indicating invalid role mapping

To work around this problem:

  1. Ensure the user is assigned a supported Keycloak group.

  2. Verify the user is mapped to a valid Measure/Release role combination.
  3. For users added to the Users group in Keycloak, use the authorization feature in Measure or Release to assign the required permissions.
  4. Re-login after correcting the configuration.
 2.0.2
NEXUS00005067 When you run the list test command, the response returns only the count of projects instead of detailed test information such as test names, IDs, or metadata. In some cases, the returned data might also be inaccurate.

Also, when you run a test prompt, the system might return a test asset file not found error even when the correct project ID and test name are provided, indicating an issue in locating or mapping the specified test file.

Currently, there is no workaround for this problem.		 2.0.2
NEXUS00006206 When you access the /teamspaces or /teamspaces/{id}/tasks API endpoints in an IHD environment, you might experience slow response times.

Currently, there is no workaround for this problem.

 2.0.2
NEXUS00006316 The Jenkins data is not available in the Deployment by Environment Name chart in Analytics Dashboards.

Currently, there is no workaround for this problem.

 2.0.2 2.0.2.1
NEXUS00004133 When you use IBM watsonX, it might not provide proper responses for multistep workflows. The issue is currently observed only with workflows involving multiple steps. Single-step workflows work as expected.

To work around this problem, you must use IBM watsonX only for single-step workflows until the issue is resolved.

 2.0.0
NEXUS00003275 When an administrator is added to a loop by another administrator before logging into Measure for the first time or before creating their own Loop, the administrator cannot log in to Measure.

To work around this problem, you must log in to Measure as another administrator (for example, the one who created the loop) and assign the global Product Administrator role to the administrator who cannot log in.

 1.0.3