NVD feed 403s once every day or two when building the vulnerabilities repo.
🕯️ More info
First step for this is probably to log the error message we get in the 403 for better troubleshooting. If there's something we're doing wrong we should fix that. Otherwise we should tweak our retry logic to retry on the types of 403s we're seeing from NVD.
Basically, we want to be as resilient as we can be to transient errors, within the context of the feed build jobs, so that if there's a failure we can treat the failure as something to fix rather than ignore, and alert accordingly.
We already have #21780 for Amazon Linux transient issues (which are actually transient), so the scope of this bug is just NVD within the context of the vulnerabilities repo.
💥 Actual behavior
NVD feed 403s once every day or two when building the vulnerabilities repo.
🕯️ More info
First step for this is probably to log the error message we get in the 403 for better troubleshooting. If there's something we're doing wrong we should fix that. Otherwise we should tweak our retry logic to retry on the types of 403s we're seeing from NVD.
Basically, we want to be as resilient as we can be to transient errors, within the context of the feed build jobs, so that if there's a failure we can treat the failure as something to fix rather than ignore, and alert accordingly.
We already have #21780 for Amazon Linux transient issues (which are actually transient), so the scope of this bug is just NVD within the context of the vulnerabilities repo.