Details
-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
None
-
quay-v3.7.9
-
False
-
None
-
False
-
Moderate
-
0
-
Customer Escalated
Description
Customer initially created a ticket with the issue of "Clair failed to deliver notifications : code: 400 status 400 Bad request" and the issue was addressed by this jira ticket
https://issues.redhat.com/browse/PROJQUAY-4002.
After applying the errata , customer is now saying they are flooding with following errors:
quay-registry-quay-app-759d9966ff-s5q56-quay-app.log:nginx stdout | 10.10.10.2 (-) - - [18/Nov/2022:22:19:29 +0000] "POST /secscan/notification HTTP/1.1" 504 167 "-" "clair/v4" (60.000 758 60.000) quay-registry--quay-app-759d9966ff-s5q56-quay-app.log:nginx stdout | 10.10.10.3 (-) - - [18/Nov/2022:22:21:29 +0000] "POST /secscan/notification HTTP/1.1" 504 167 "-" "clair/v4" (60.000 758 60.001) bash-4.4$ grep -i "" 4.." quay-registry-quay-app-759d9966ff*.log quay-registry-quay-app-759d9966ff-fpp6j-quay-app.log:nginx stdout | 10.10.10.3 (-) - - [18/Nov/2022:22:18:29 +0000] "POST /secscan/notification HTTP/1.1" 499 0 "-" "clair/v4" (60.002 758 60.001) quay-registry-quay-app-759d9966ff-fpp6j-quay-app.log:nginx stdout | 10.10.10.2 (-) - - [18/Nov/2022:22:20:29 +0000] "POST /secscan/notification HTTP/1.1" 499 0 "-" "clair/v4" (60.001 758 60.001)
