Skip to content
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

Bug Report: When delete pod the related "PodGroup" won't be deleted #755

Closed
xiaogaozi opened this issue Apr 3, 2020 · 0 comments · Fixed by #756
Closed

Bug Report: When delete pod the related "PodGroup" won't be deleted #755

xiaogaozi opened this issue Apr 3, 2020 · 0 comments · Fixed by #756
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@xiaogaozi
Copy link
Contributor

Is this a BUG REPORT or FEATURE REQUEST?:

/kind bug

What happened:

When create Pod with Volcano as scheduler, Volcano controller will create a PodGroup automatically for this pod. The OwnerReferences field of this PodGroup will set to original pod. But BlockOwnerDeletion field in OwnerReference not set, so its value will be default value (i.e. false). Reference to official K8s document, only object with BlockOwnerDeletion set to true will be deleted when in cascading deletion. So when delete original pod the related PodGroup won't be deleted.

What you expected to happen:

Delete pod will delete related PodGroup also.

How to reproduce it (as minimally and precisely as possible):

Create a Pod and set schedulerName to volcano, then delete the pod see if related PodGroup deleted also.

Anything else we need to know?:

N/A

Environment:

  • Volcano Version: v0.3
  • Kubernetes version (use kubectl version): v1.14.6
  • Cloud provider or hardware configuration: N/A
  • OS (e.g. from /etc/os-release): N/A
  • Kernel (e.g. uname -a): N/A
  • Install tools: N/A
  • Others: N/A
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants