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

Containers are already terminating while drain scripts of other jobs in the instance group are still running #1706

Open
jandubois opened this issue Mar 12, 2021 · 3 comments
Labels
Type: Bug Something isn't working
Milestone

Comments

@jandubois
Copy link
Member

This is a bug in quarks-operator: cloudfoundry-incubator/quarks-operator#1297

Just creating a corresponding kubecf issue so we can track it for the 2.8.0 release milestone.

@jandubois jandubois added the Type: Bug Something isn't working label Mar 12, 2021
@jandubois jandubois added this to the 2.8.0 milestone Mar 12, 2021
@jandubois jandubois assigned gaktive and unassigned gaktive Mar 12, 2021
@univ0298
Copy link
Contributor

I know this is just a shadow defect so it's not that important.. but FWIW the title of this issue is a bit misleading. Individual containers do not terminate while their drain scripts are running. The problem is specifically that each individual container will terminate once it's own drain script ends (or immediately if it has no drain script). Instead each container in a pod should wait for all other containers in the pod to finish their drains before any container terminates.

@jandubois jandubois changed the title Containers are terminated while drain scripts are still running Containers are already terminating while drain scripts of other jobs in the instance group are still running Mar 16, 2021
@jandubois
Copy link
Member Author

I've tried to improve it, but it is hard to fit the whole story into the subject line...

Anyways, this issue only exists so I could add it to the 2.8.0 Milestone.

@univ0298
Copy link
Contributor

looks good!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants