Chapter 5. Known issues

RHDH cannot push content to the GitOps repository on GitHub

When you create an application, RHADS - SSC automatically creates a GitOps repository on GitHub. However, in some cases, RHDH fails to push content into this repository. As a result, a pipeline for this application fails with an error. To work around, restart the application creation process.

Creating a new component can fail at the Create ArgoCD Resources step

When you create a new component, the pipeline might fail at the Create ArgoCD Resources step with an error invalid json response body. At the moment, there is no workaround. Try recreating this component until the pipeline is successful.

Two container images for Tekton Tasks Steps are not signed

RHADS - SSC uses Tekton as the default CI provider. A Tekton pipeline is a collection of Tasks that consist of multiple Steps, and each Step runs a certain container image. Most of these images are stored in the trusted Red Hat Ecosystem Catalog, accessible via registry.redhat.io or registry.access.redhat.com. However, the following two images are not stored in these registries and are not signed:

RHDH doesn’t display the Image Registry tab if RHADS - SSC cannot detect your registry type

The Red Hat Developer Hub UI doesn’t display the Image Registry tab on the component’s page if RHADS - SSC is unable to detect which container image registry you’re using. RHADS - SSC analyzes your registry URL to annotate your components, and if that annotation is missing, the tab will not appear in the RHDH UI. To work around this issue, you can manually enable the Image Registry tab.

The RHDH UI displays an incorrect JFrog Artifactory container image link

When you create a new component while using the JFrog Artifactory container registry, the RHDH UI displays an incorrect container image link. After a successful pipeline run, it’s expected that selecting View Output in the Actions menu shows build details including the correct image link. The actual behavior is that the link is incorrect, and there is no workaround for this issue at this time.

Azure pipelines logs aren’t available in RHDH

Currently, if you use Azure as a CI provider, the RHDH UI doesn’t show build logs for Azure pipelines. This issue occurs because RHDH 1.6 uses an older version of the Azure Devops plugin, backstage-community-plugin-azure-devops-backend-dynamic, which doesn’t support fetching logs. There is no workaround in RHDH 1.6, however logs retrieval is available in a newer version of the plugin and may be included in a future release.

Opening a pull request triggers two pipelines in Azure CI

Currently, for Azure CI, when you push changes to either the gitops-repo or source-repo repositories, two pipelines are triggered. To work around this issue, disable unwanted pipeline runs by toggling the Disable implied YAML CI trigger setting as described in Prevent unintended pipeline runs in the Azure DevOps documentation.

The CI tab shows unrelated Azure pipelines

When you’ve created a new component while using Azure CI, the CI tab may incorrectly display pipelines unrelated to a newly created component but associated with other components in the same Azure DevOps project. This occurs because no Azure pipeline has been triggered for the new component, and there are no pipelines linked to it. Once the first pipeline is triggered, the CI tab will correctly display the associated pipeline.

When buildDefinition is not found, Azure CI lists all existing builds

In Azure CI, if you set the dev.azure.com/build-definition annotation on the component and then list the builds, the list is expected to show only builds for a specified pipeline. If Azure Pipelines can’t find a pipeline with a matching name, it should return no builds. However, the current behavior is that all unrelated builds are returned. At the moment, there is no workaround.

GitHub details are missing for Jenkins pipeline runs

After a Jenkins pipeline run for a component is complete, the Projects/Run view in the CI tab may display empty fields for Message, Author, and GitHub, even though the GitHub Commit ID is correctly displayed. This issue occurs because the current version of the RHDH Jenkins plugin doesn’t retrieve all required information. Currently, there is no workaround.

The CI tab displays GitLab CI information for Tekton and Jenkins

When you host source code for your component in GitLab and choose Tekton or Jenkins as a CI provider, the CI tab in the RHDH UI may incorrectly display information about GitLab pipelines together with the Tekton or Jenkins pipelines. Note that if you choose Tekton or Jenkins, RHADS - SSC only runs Tekton or Jenkins pipelines, and the CI tab section about GitLab pipelines should be ignored.

RHDH doesn’t display the Image Check tab if you use GitLab CI

If you use GitLab CI as a CI provider, the CI page in the RHDH UI may not display the Image Check tab and the component’s container image URL. However, the Image Scan and Deployment Check tabs are displayed correctly. Currently, there is no workaround.

RHADS - SSC doesn’t support some environments

RHADS - SSC 1.6 does not support the following environments: any air-gapped environment, IBM Power Platform, IBM Z Platform, ARM64, and Federal Information Processing Standards (FIPS) mode OCP.

Uninstallation of RHADS - SSC is not supported

Uninstallation of RHADS - SSC is not currently supported, but it can be done by removing all rhtap namespaces from the cluster.