이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 4. Known issues
A list of known issues found in this release of Red Hat Trusted Profile Analyzer:
Package version mismatch between the API response and the HTML report for Red Hat Dependency Analytics
Opening a manifest file for analysis in Visual Studio Code or IntelliJ, can give you a different package version number between the Red Hat Dependency Analytics (RHDA) HTML report and an API client response. Before analyzing the manifest file, the API client compares package versions in the manifest file to the installed package versions within the client’s environment. When there is a difference in package version, you receive an error message containing the first package version mismatch. To workaround this issue, you can disable the Match Manifest Versions option of RHDA extension in your integrated development environment (IDE).
Inconsistencies between the total number of CVEs displayed on the dashboard and the CVE tab
The total number of Common Vulnerabilities and Exposures (CVE) uses different filters between the RHTPA home page dashboard and the CVE tab on the search results page, causing the discrepancy between the two values. Currently, there is no workaround for this known issue.
Data migration fails when upgrading from Trusted Profile Analyzer 1.1.2 to 1.2
The bombastic and vexation collector pods crash when there is no space left on the persistent volume claim (PVC) for the PostgreSQL instance. To workaround this potential issue, increase the size of the PVC by 10 GB.
A timeout error occurs when doing an SBOM bulk upload
When doing a software bill of materials (SBOM) bulk upload, this causes the SBOM dashboard to fail when loading, giving a connection timeout error. Currently, there is no workaround for this issue.
SBOM data does not load properly when uploading a large SBOM
When uploading a large software bill of materials (SBOM) documents, for example an SBOM that includes 50,000 packages, the RHTPA dashboard does not load properly. This happens because of Keycloak’s access token expiring before the SBOM can finish uploading its data. To workaround this issue, you can increase the lifespan of Keycloak’s access token, and then redeploy Keycloak:
- Log in to the OpenShift cluster from the command-line interface.
Find Keycloak’s URL string:
echo https://$(oc get route keycloak -n keycloak-system | tail -n 1 | awk '{print $2}')/auth- Copy and paste the URL string from the earlier step into a web browser, and go to the authentication page.
Log in to the Keycloak Administration Console.
NoteYou can find the user credentials in the OpenShift web console by expanding the Workloads menu, click Secrets, and click your Keycloak instance name.
- On the home page, click Realm Settings, and select the Tokens tab.
- Change the Access Token Lifespan value from the default of 5 minutes, to 60 minutes, and save the change.
Redeploy Keycloak:
oc scale deployment/keycloak-postgresql --replicas=0 oc scale deployment/rhsso-operator --replicas=0 oc scale deployment/keycloak-postgresql --replicas=1 oc scale deployment/rhsso-operator --replicas=1
- Try uploading your SBOM again.
An API error on the package details page
In the RHTPA console, when navigating from the Vulnerabilities page to the package details page, clicking the affected dependencies link gives you the following error message:
API error: Error contacting GUAC (Guac) - Client error: Cannot find an SBOM for PackageUrl
Currently, there is no workaround for this known issue.
