Instances of the long running cluster have seen

$ ks logs central-db-66b47599d6-kdsbf | grep -i error
Defaulted container "central-db" out of: central-db, init-db (init)
2025-06-26 06:28:49.366 UTC [102438] ERROR:  duplicate key value violates unique constraint "image_cves_v2_pkey"
2025-06-26 08:07:00.050 UTC [105846] ERROR:  duplicate key value violates unique constraint "image_cves_v2_pkey" 

This has been reported in the following slack threads for the same issue:

https://redhat-internal.slack.com/archives/C033Z8KMZAM/p1750959463839389

https://redhat-internal.slack.com/archives/C01DQH7UP8C/p1750959664434249

https://redhat-internal.slack.com/archives/C05S6AALVJM/p1750961710068419

For this to occur within a single image the component and the CVE would have to be identical as the key for the CVE includes the component ID which includes a hash of the component and the CVE ID includes a hash of the CVE.  It is entirely possible that this is a data issue from our generated data, but since it is easy to address it can be addressed.