-
Bug
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
Quay Enterprise
-
Undefined
-
-
0
Quay/Clair 3.3.1
we see following error in Clair logs
{"Event":"could not get NVD data feed hash","Level":"warning","Location":"nvd.go:161","Time":"2020-10-06 01:17:55.343556","data feed name":"2018","error":"https://nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2018.meta failed status code: 404"}
{"Event":"could not get NVD data feed hash","Level":"warning","Location":"nvd.go:161","Time":"2020-10-06 01:17:55.650280","data feed name":"2019","error":"https://nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2019.meta failed status code: 404"}
{"Event":"could not get NVD data feed hash","Level":"warning","Location":"nvd.go:161","Time":"2020-10-06 01:17:55.902132","data feed name":"2020","error":"https://nvd.nist.gov/feeds/json/cve/1.0/nvdcve-1.0-2020.meta failed status code: 404"}
This has been fixed in upstream with fix https://github.com/quay/clair/commit/5fe11e67793b9508a0fe4fe8f0b6ec5bd358cdd0 ,so we need the same fix in downstream aswell, since it breaking all the nvd feeds for lot of users
