-
Notifications
You must be signed in to change notification settings - Fork 716
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
TfJob should be marked as failed if setup fails #218
Labels
Comments
So I can repo this using the following spec:
Which results in the following job
The state isn't set but it should be set to failed. |
jlewi
added a commit
that referenced
this issue
Dec 15, 2017
* Fixes #218 * If a job can't be initialized (e.g. because the spec is invalid) the state should be set to failed. * I refactored the code so that in the event that the call to setup fails, it will end up getting retried as part of the next attempt at reconcilation * I moved the call to setup into run * We also refactored the code for reconciling the state into a separate function reconcile. I did this because we want to call reconcile when run is first invoked and not wait for the reconcile interval to elapse. * Delete the method triggerCreatePhase; I moved the relevant code for setting the phase into setup. * Delete some code that is a legacy of the etcd-operator and no longer being used.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context #203
Added event is recieved
tfjobs.yaml.txt
Ideally we should have an E2E test to verify the correct behavior.
The text was updated successfully, but these errors were encountered: