-
Notifications
You must be signed in to change notification settings - Fork 5k
Open
Description
Versions:
- harbor version: v2.14.0-44a74424
- docker engine version: goharbor/harbor-core:v2.14.0
Additional context:
Just now, upgraded from v2.13.1-9384ed0e.
Using harbor from the official Helm chart in Kubernetes 1.30.x
I am unable to scan container images for vulnerabilities due to the following error:

Log messages from the scan (clicking the error icon)
2025-10-18T20:03:29Z [INFO] [/pkg/scan/job.go:396]: {
"uuid": "d1e51b66-90b2-11eb-824d-160956cf7d3a",
"name": "Trivy",
"description": "The Trivy scanner adapter",
"url": "http://harbor-trivy:8080",
"disabled": false,
"is_default": true,
"health": "healthy",
"auth": "",
"access_credential": "[HIDDEN]",
"skip_certVerify": false,
"use_internal_addr": true,
"adapter": "Trivy",
"vendor": "Aqua Security",
"version": "v0.66.0",
"create_time": "2021-03-29T17:18:46.496385Z",
"update_time": "2024-10-02T03:51:59.469822Z"
}
2025-10-18T20:03:29Z [INFO] [/pkg/scan/job.go:396]: {
"registry": {
"url": "http://harbor-core:80",
"authorization": "[HIDDEN]",
"insecure": false
},
"artifact": {
"namespace_id": 1,
"repository": "library/ubuntu",
"tag": "latest",
"digest": "sha256:c6217a0629e71759c810b55f38969fa82b7a49b76652ab23ba6217860d8b227e",
"mime_type": "application/vnd.docker.distribution.manifest.v2+json",
"size": 30596313
},
"enabled_capabilities": [
{
"type": "vulnerability",
"produces_mime_types": [
"application/vnd.security.vulnerability.report; version=1.1"
],
"parameters": null
}
]
}
2025-10-18T20:03:29Z [INFO] [/pkg/scan/job.go:172]: Report mime types: [application/vnd.security.vulnerability.report; version=1.1]
2025-10-18T20:03:29Z [INFO] [/pkg/scan/job.go:229]: Get report for mime type: application/vnd.security.vulnerability.report; version=1.1
2025-10-18T20:03:31Z [ERROR] [/pkg/scan/job.go:307]: handler failed at PostScan, report e377dd21-efc0-4144-850a-3678cddf8d50, error Error when converting vulnerability report: ERROR: column t0.status does not exist (SQLSTATE 42703)
Not sure if our tables are messed up, but I can see from the database migrations a "status" column was dropped from the scan_report table way back in 2.2.0.
ALTER TABLE scan_report DROP COLUMN IF EXISTS status; |
Could this be related?
Best regards.
Metadata
Metadata
Assignees
Labels
No labels