Chapter 5. Known issues This section describes known issues in Red Hat Trusted Application Pipeline 1.4. Pipeline fails if you create a new Deployment Namespace When you create a new component with a new Deployment Namespace, the pipeline fails with the error tasks.tekton.dev "rhtap-dev-namespace-setup" not found . To work around this issue, use the default Deployment Namespace called rhtap-app . 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 . Jenkins can only use one Git hosting provider The default Jenkins configuration uses a global credential called GITOPS_AUTH_PASSWORD to authenticate when updating the gitops repository with a newly built image. Because only one such global variable is available, a single Jenkins instance can only be configured to work with one Git repository provider at a time, GitHub, GitLab, or Bitbucket Cloud. 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. The CD and Docs tabs show an error for the GitOps resource In the Red Hat Developer Hub UI, the CD and Docs tabs for the GitOps resource don't generate the expected content and display an error. The Workflow file in the -gitops repository doesn't point to secrets When you create a new component and use GitHub Actions as a CI provider, RHTAP generates a GitHub repository with your component. This repository contains a <your-component-name>-gitops folder with the Workflow file, which should provide a list of environment variables and references to secrets. Currently, only a list of variables is present in the Workflow file. The task order in the CI templates is incorrect In the Jenkins, GitLab CI and GitHub Actions templates, the update-deployment task runs after the acs-deploy-check task. This order is unexpected and doesn't align with the Tekton pipeline configuration. RHTAP doesn't support some environments RHTAP 1.4 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. Revised on 2025-02-06 16:32:22 UTC

Commands: