fleetdm
🪲Missing primary key for vulnerability_host_counts table
Fleet version: 4.67
Web browser and operating system: N/A
💥 Actual behavior
Self-hosted users have reported receiving alerts that the vulnerability_host_counts table is missing a primary key.
🧑💻 Steps to reproduce
- TODO
🕯️ More info (optional)
N/A
Linked to Unthread ticket:
@mostlikelee Does this need more investigation? Not sure if the Unthread ticket is enough context?
I believe the core issue here is a missing primary key generates a lot of warning logs. I'll confirm with the infra team.
https://fleetdm.slack.com/archives/C051QJU3D0V/p1753732438804589
@mason-buettner the slack thread didn't have any info on the impact of the missing key. Can you get more info here?
@mostlikelee I believe the extent of the impact was the generation of warning logs. I'll confirm with customer-blanco.
@mostlikelee confirmed that there was no further impact beyond the warnings.
@mason-buettner looking at the empty repro steps, I'm assuming you haven't been able to reproduce.
If you have repro steps, please add them!
@mostlikelee @jmwatts sending the bug back to the "Inbox" state to help with repro: https://fleetdm.com/handbook/company/product-groups#inbox
@mostlikelee we spoke with customer-blanco and asked for further info for reproduction. At this time the impact is limited to warnings, and we're going to close this ticket until we can get further information to enrich this report.
Key lost in the cloud, Fleet finds, secures anew. Users breathe, relieved.
