Bug 1583707

Summary: Orphaned pod found, but volumes not yet removed on OCP 3.7
Product: OpenShift Container Platform Reporter: Sunil Choudhary <schoudha>
Component: StorageAssignee: Hemant Kumar <hekumar>
Status: CLOSED CURRENTRELEASE QA Contact: Liang Xia <lxia>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.7.1CC: agawand, andcosta, aos-bugs, aos-storage-staff, bchilds, clichybi, hekumar, joboyer, lxia, mnoguera, nnosenzo, openshift-bugs-escalate, schoudha, sychen, tcarlin, vjaypurk
Target Milestone: ---   
Target Release: 3.7.z   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1654532 (view as bug list) Environment:
Last Closed: 2019-02-19 21:41:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1558600, 1654532    

Description Sunil Choudhary 2018-05-29 14:07:22 UTC 
With reference to BZ 1508578 , opening this BZ for OCP 3.7

We are observing orphaned pod messages in OCP 3.7 when scaling down DC and it takes around 3-4 minutes to terminate pods. Sometime it takes even more time.

Orphaned pod "1e42a2e7-6256-11e8-9a54-68b5996caa9e" found, but volumes not yet removed.  Reducing cpu to minimum

This is observed when node is running large number of pods (around 150 - 200) but resources like CPU, memory, etc are not exhausted.

The orphaned pod messages does stop when pod is terminated.
Comment 2 Bradley Childs 2018-05-29 15:29:23 UTC 
*** Bug 1508578 has been marked as a duplicate of this bug. ***
Comment 10 Hemant Kumar 2019-02-19 21:41:05 UTC 
Closing this since the the fix requires a large backport and impact is minimal. If you need automation piece done by storage/engineering team, please open separate bug.