-
Notifications
You must be signed in to change notification settings - Fork 700
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
"invalid memory address or nil pointer dereference" #1382
Comments
/kind bug |
Let me have a look at the common. |
Seems that https://github.com/kubeflow/common/blob/9d86006b1ee7d5eb9e9ee4023858cc3398877ad0/pkg/controller.v1/common/job.go#L429 PriorityClassLister is not initialized correctly. |
Signed-off-by: cegao <cegao@tencent.com>
* feat(init): Initialize podpriority Signed-off-by: cegao <cegao@tencent.com> * fix(priority): Fix #1382 Signed-off-by: cegao <cegao@tencent.com>
@gaocegege Is gang scheduling used in this issue? |
Yes, the operator will crash if gang is enabled. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
old tf-operator version is v0.5.3 , I only upgrade tf-operator controller without upgrading crd/serviceacccount etc.
new tf-operator image is
public.ecr.aws/j1r0q0g6/training/tf-operator:47a74b738920edbf4207160cec7e1dff9cdab3f2
when I create tfjob
tf-operator container logs
The text was updated successfully, but these errors were encountered: