이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 5. Known issues


This section describes known issues in Red Hat Trusted Application Pipeline 1.3.

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.

Vulnerabilities tab in RHTPA may show Internal server error

When RHTAP uploads the SBOM to Red Hat Trusted Profile Analyzer, RHTPA accepts the SBOM but may show Internal server error in the Vulnerabilities tab. If you encounter this issue, contact rhtpa-support@redhat.com.

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.

RHTAP doesn’t automatically find a Rekor server when running Jenkins pipelines

When running a Jenkins pipeline, RHTAP cannot find a Rekor server if your Jenkins instance runs outside the RHTAP cluster. To work around this problem, you must manually provide the external routes for the Rekor and TUF services by configuring the REKOR_HOST and TUF_MIRROR environment variables in the env.sh file. Their values should include your cluster URL. For details and instructions, refer to Customizing sample software templates for Jenkins.

Note

GitLab: If RHTAP cannot reach the Rekor and TUF services when running GitLab pipelines, check that you’ve added their correct URLs as CI/CD variables in GitLab. For instructions, refer to Adding secrets to GitLab CI for secure integration.

When you use GitLab, you might see an error: namespaces "rhtap-acs" not found

When you use GitLab as an authentication option, a Git hosting platform and a CI provider, and you also disable ACS and integrate Quay, at the end of the RHTAP installation you might see the following error:

[INFO] Configure internal Quay integration with internal ACS
Error from server (NotFound): namespaces "rhtap-acs" not found

Despite this error, RHTAP is installed correctly and its functionality isn’t affected.

RHTAP doesn’t support some environments

RHTAP 1.3 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 2024-12-12 18:58:38 UTC

Red Hat logoGithubRedditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

© 2024 Red Hat, Inc.