Report for builds with wrong content_set.yml
You received this email because at least one released brew build does not have valid data in content_set.yml. It is an optional test in CVP but there is a plan to make it required in the beginning of August 2020

There are security implications if the information in content_set.yml is incorrect. For example, Freshmaker may fail to rebuild a vulnerable image, or even detect that the image is vulnerable. Worse yet, Clair also relies on this information, indirectly via CPEs. Redundant content sets may lead to false negatives in grading. Missing content sets may lead to false positives in grading. Images that have already been released with incorrect content sets can't be fixed. These will require rebuild and re-release of such containers to correct the grading.

You can find more information about content sets on the OSBS page

Such email is sent to many users. If you cannot fix the issue please ensure that right people are aware of the issue and the issue is appropriately prioritized in the team.

Please contact cvp-ops@redhat.com if you have any questions or concerns, or you can add a comment to CVP issue for making the content_set check required.