Chapter 5. Known issues

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

RHTAP 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:

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

In Azure Pipelines, 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.

View logs and View SBOM icons don’t link to correct information

After a Pipeline Run is finished, you should be able to access the build summary and SBOM by clicking the View logs and View SBOM icons in the Actions menu. However, these icons don’t always show the correct information. To access the correct steps in logs, click either of these two icons, and in the pop-up window with logs, select the step you need: show-sbom or show-summary.

RHDH doesn’t display the Image Registry tab if RHTAP cannot detect your registry type

The Red Hat Developer Hub UI doesn’t display the Image Registry tab on the component’s page if RHTAP is unable to detect which container image registry you’re using. RHTAP 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 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, RHTAP only runs Tekton or Jenkins pipelines, and the CI tab section about GitLab pipelines should be ignored.

RHTAP doesn’t support some environments

RHTAP 1.5 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 RHTAP is not supported

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