Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 3. Known issues
-
Installation might fail due to a known issue with RHTAP SecureSign. To recover, simply delete the namespace into which you’ve deployed RHTAP (
rhtapby default) and rerun the installer. On the second run, the installation should be successful. -
You can configure GitLab as an authentication provider in the
private-values.yamlfile you create for installation. However, once GitLab is configured, it still doesn’t show up as a sign in option. The login for GitLab is accessible in the settings page,<host>/settings/auth-providers, but requires signing in to GitHub to access that page. -
The
pull-requestpipeline often fails with thebuild-containertask and displays the following error message:Access to the requested resource is not authorized. To fix this, push your container image to Quay.io and run the pipeline again. When promoting applications, the
verify-enterprise-contracttask currently fails. However, to fix this issue, you simply need to remove the Rekor custom resource (CR). A new Rekor CR then starts up, but the task no longer fails. Remove the CR with one of the following methods:Delete the Rekor CR in your command line.
oc delete rekor -n $<namespace where rhtap is installed> rhtap-securesign-
In the OCP console, in the Admin view, click on Search under the Home tab. Search for "Rekor" in the
rhtapnamespace, and delete the instance of the CR that you find.
-
When you promote a new container image to the RHTAP stage environment from a Go or Python software template, you run the
verify-enterprise-contractstep. This step might cause the following error:No image attestations found matching the given public key.You must manually update the image repository so that it’s public. - RHTAP 1.0 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 currently supported, but it can be done by removing all RHTAP namespaces from the cluster.
Revised on 2024-07-01 13:32:22 UTC
