You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But it turns out that there is no longer a repo at registry.redhat.io/rh-acs
The images have all moved to registry.redhat.io/advanced-cluster-security/
Because of this, the cve-analyser is not able to lookup information about the RHACS images. As an example, here is a sample input:
CVE-2023-0361,rh-acs/main,CVE Severity:Moderate,Not Found Any Information
CVE-2023-0361,rh-acs/main:3.74,CVE Severity:Moderate,Not Found Any Information
CVE-2023-0361,advanced-cluster-security/rhacs-main-rhel8,CVE Severity:Moderate,Not Found Any Information
CVE-2023-0361,advanced-cluster-security/rhacs-main-rhel8:3.74,CVE Severity:Moderate,(Red Hat Enterprise Linux 8|Product impact:moderate|Affected|gnutls)
Only in the case where the advanced-cluster-security repo is used along with the tag is processing completed. This is not a flaw in the cve-analyser but rather an issue with how the RHACS containers were moved in the registry vs how they are shown in the operator catalog. I intend to submit a BZ against RHACS to resolve this issue if possible.
The text was updated successfully, but these errors were encountered:
Using oc-mirror we can look at the images for Red Hat Advanced Cluster Security here:
But it turns out that there is no longer a repo at registry.redhat.io/rh-acs
The images have all moved to registry.redhat.io/advanced-cluster-security/
Because of this, the cve-analyser is not able to lookup information about the RHACS images. As an example, here is a sample input:
And sample output
Only in the case where the advanced-cluster-security repo is used along with the tag is processing completed. This is not a flaw in the cve-analyser but rather an issue with how the RHACS containers were moved in the registry vs how they are shown in the operator catalog. I intend to submit a BZ against RHACS to resolve this issue if possible.
The text was updated successfully, but these errors were encountered: