You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In AWX i'm experimenting with longer image pending timeout times, because I want to be able to use resource requests and let the jobs get scheduled as resources are available.
But that means that I want Pending jobs to really be Pending.
We have a test case where we try and start a job with a image we know is not pullable because it requires a pull secret we don't configure correctly.
The expecation is that this job fails. Currently, it only does this if we exceed the pod pending timeout, but it should fail sooner.
In AWX i'm experimenting with longer image pending timeout times, because I want to be able to use resource requests and let the jobs get scheduled as resources are available.
But that means that I want Pending jobs to really be Pending.
We have a test case where we try and start a job with a image we know is not pullable because it requires a pull secret we don't configure correctly.
The expecation is that this job fails. Currently, it only does this if we exceed the pod pending timeout, but it should fail sooner.
Example:
This work unit has the status Pending:
But the status in kubernetes is:
This type of error generally does not resolve itself, and we should move the work unit status to Error with the detail of "Image pull backoff"
The text was updated successfully, but these errors were encountered: