-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The scan status displays 'Scanning,' even though the job has reached the specified backoff limit #2326
Labels
bug
Bugs
Comments
Alon-Katz
changed the title
Scan shows state "Scanning" while Job has reached the specified backoff limit
The scan status displays 'Scanning,' even though the job has reached the specified backoff limit.
Mar 3, 2024
Alon-Katz
changed the title
The scan status displays 'Scanning,' even though the job has reached the specified backoff limit.
The scan status displays 'Scanning,' even though the job has reached the specified backoff limit
Mar 3, 2024
Oh mh interessting, we'll have a look. |
Ilyesbdlala
added a commit
that referenced
this issue
Jul 9, 2024
…d due to exceeding the backoff limit we had the assumption that job.Status.Failed calculates the number of times the job failed. it is actually the number of pods that failed due to this job. In this case it will always be a max of 1. Supplemented it with job.Status.Conditions[].Reason Signed-off-by: Ilyes Ben Dlala <[email protected]>
4 tasks
Weltraumschaf
pushed a commit
that referenced
this issue
Jul 31, 2024
…d due to exceeding the backoff limit we had the assumption that job.Status.Failed calculates the number of times the job failed. it is actually the number of pods that failed due to this job. In this case it will always be a max of 1. Supplemented it with job.Status.Conditions[].Reason Signed-off-by: Ilyes Ben Dlala <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐞 Bug report
Describe the bug
The scan job created by the scan CRD is in a failed state with the event: 'Job has reached the specified backoff limit.' However, the scan CRD continues to display a 'Scanning' status and does not update to 'Failed.'
The latest version included a bug fix intended to address the issue 'Fixed Scans being marked as Failed after the first job has failed,' which may be relevant.
Unfortunately, this fix seems to have exacerbated the problem, as now scans are incorrectly showing a 'Scanning' status when they have actually failed.
ref to the bug fix: #2205
Steps To Reproduce
Run a scan that is failing, look at the job events, view the scan status
Expected behavior
If the job has reached the maximum backoff limit, the scan status should be "Failed" and not "Scanning"
System (please complete the following information):
v4.4.1
kubectl version
]:Client Version: v1.29.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.5-eks-5e0fdde
Screenshots / Logs
Job output:
Scan output:
The text was updated successfully, but these errors were encountered: