Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1690307 - Deleted Pods still contain stale containers
Summary: Deleted Pods still contain stale containers
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Pod
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.11.z
Assignee: Seth Jennings
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-19 09:25 UTC by Jaspreet Kaur
Modified: 2019-04-09 19:32 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Jaspreet Kaur 2019-03-19 09:25:29 UTC
Description of problem: sometimes we have been forced to kill (grace-period=0 and sometimes force) pods that stay in terminating state forever.
But almost always, when the pod does not terminate by its own and we have to force the kill as above, the pod disappears but the container(s) still runs and is visible by docker ps.
This has led , for example to duplicated cassandra containers (the old one and the new one) waisting resources or sometimes blocking the creation of the new pod (volumes still in use for example).



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: Containers are present even if the pods are deleted.

Expected results:  Containers should be removed along with the Pods deletion.



Additional info: Alsom If there is a single way to find out all the stale and orphaned containers.


Note You need to log in before you can comment on or make changes to this bug.