Skip to content
This repository has been archived by the owner on Sep 24, 2021. It is now read-only.

Clean up sandbox checkpoint and network plugin properly #87

Closed
feiskyer opened this issue Mar 14, 2017 · 0 comments · Fixed by #90
Closed

Clean up sandbox checkpoint and network plugin properly #87

feiskyer opened this issue Mar 14, 2017 · 0 comments · Fixed by #90

Comments

@feiskyer
Copy link
Contributor

Currently, sandbox checkpoint is only removed after the pod is deleted successfully. However, if the hyper pod has already been removed outside, the checkpoint will be left over and kubelet will always fail on stopping sandbox.

We should ensure checkpoint and network plugin are cleaned up properly once frakti has detected the sandbox has already been non-exist.
heartlock added a commit to heartlock/frakti that referenced this issue Mar 15, 2017
@heartlock
fix kubernetes-retired#87 clean up checkpoint once sandbox non-exist
f899137
@heartlock heartlock mentioned this issue Mar 15, 2017
Merged
heartlock added a commit to heartlock/frakti that referenced this issue Mar 15, 2017
@heartlock
fix kubernetes-retired#87 clean up checkpoint once sandbox non-exist
bc06728
feiskyer added a commit that referenced this issue Mar 16, 2017
@feiskyer
Merge pull request #90 from heartlock/fix-bug-#87
6cb84cb 
fix #87 clean up checkpoint once sandbox non-exist
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix #87 clean up checkpoint once sandbox non-exist heartlock/frakti
1 participant
@feiskyer