-
Notifications
You must be signed in to change notification settings - Fork 699
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
[v1alpha2] Invalid Job spec crashes operator #706
Comments
Here's the valid spec.
Can we avoid crashing the operator and instead add an error message to the status? I though we added some handling with v1alpha2 to do that |
/assign @codeflitting |
@gaocegege: GitHub didn't allow me to assign the following users: codeflitting. Note that only kubeflow members and repo collaborators can be assigned. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@jlewi Could you please invite @codeflitting and @yph152 as Kubeflow members? I can not assign issues to them. |
Invites sent |
/assign @codeflitting |
@codeflitting Thanks. Rather than manually verifying it, do we have a test that checks invalid specs are handled properly? If not how about opening an issue to add one. |
Yes we have, I have wrote more test cases to cover the validation (#711) |
Yeah, I think we could close the issue. If we meet again we could reopen it. |
The following spec (I assume its invalid) is causing TFJob operator to crash
Here are the operator logs
Docker image is
The text was updated successfully, but these errors were encountered: