-
Notifications
You must be signed in to change notification settings - Fork 997
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
Pods remain in Completing
state, inconsistent with specified lifecycle policy
#1956
Comments
for this job the pods reached completed state after about an hour |
controller logs: https://gist.github.com/kye308/d1fe5526cf08b2e2cdf44e0323e4770a |
scheduler logs: https://gist.github.com/kye308/a1115373a9821d0794254b672f0761ea |
/cc |
Please use the volcano version after this commit |
@hwdef we are using the v1.4.0 tag which appears to include this change already. Is my understanding correct? |
Yes, 1.4.0 includes this commit, may be caused by other reasons. |
@hwdef @shinytang6 We need to try to reproduce the issue based on kye308's input in our envrionment. |
Hi all, I was able to fix this issue by cherry-picking #1719. Would it be possible to cherry-pick that change into the v1.4.0 release? |
@kye308 Sure. It's reasonable to cherry-pick it to v1.4.0. |
@william-wang do you have any estimate on when this can be included in the v1.4.0 release on dockerhub? |
@kye308 The bugfix has been merged to release-1.4 branch. We planed to update the image on dockerhub this week. |
@william-wang 👍 thanks for the update |
@william-wang any updates on the dockerhub image? would it include this change as well: #2026 |
Hello 👋 Looks like there was no activity on this issue for last 90 days. |
Closing for now as there was no activity for last 60 days after marked as stale, let us know if you need this to be reopened! 🤗 |
What happened: Pods in a job remain in
Running
even though another task with policyCompleteJob
onTaskSucceeded
has completed.What you expected to happen: Pods are completed after the task has completed.
How to reproduce it (as minimally and precisely as possible):
vcjob yaml used
vcjob status
Pods finally were completed after almost 24 hours.
Anything else we need to know?:
This was previously working on version 1.3.0. Pods would be marked completed within 10 minutes.
Environment:
The text was updated successfully, but these errors were encountered: