Bug 1509960

Summary:	"Orphaned pod "<pod id>" found, but volume paths are still present on disk" this error occuring continuously
Product:	OpenShift Container Platform	Reporter:	mmariyan
Component:	Storage	Assignee:	Hemant Kumar <hekumar>
Status:	CLOSED DUPLICATE	QA Contact:	Jianwei Hou <jhou>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.6.1	CC:	aos-bugs, aos-storage-staff, bchilds, tatanaka
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:	openshift container platform 3.6
Last Closed:	2017-11-06 17:37:18 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:

Description mmariyan 2017-11-06 13:00:58 UTC

Description of problem:

getting error like   " Orphaned pod "<pod id>" found, but volume paths are still present on disk "

logs:
 atomic-openshift-node: E1023 16:03:30.500035    2437 kubelet_volumes.go:114] Orphaned pod "xxxxxxxxxxxxxxxxxx" found, but volume paths are still present on disk.
 atomic-openshift-node: E1023 16:03:32.509897    2437 kubelet_volumes.go:114] Orphaned pod "xxxxxxxxxxxxxxxxxx" found, but volume paths are still present on disk.

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

 openshift container platform 3.6

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
 as above

Expected results:

the customer observed such logs in messages and node logs, it should not be occur

Additional info:

Comment 2 Bradley Childs 2017-11-06 17:37:18 UTC


*** This bug has been marked as a duplicate of bug 1508578 ***

Comment 4 mmariyan 2017-11-09 07:14:04 UTC

this bug [0] is reported on OCP 3.7, and scheduled to be fixed in 3.8.
We're currently on 3.6 .Once fixed we would like a hotfix for 3.6 on this.

[0]https://bugzilla.redhat.com/show_bug.cgi?id=1508578

Comment 5 Takayoshi Tanaka 2018-06-07 05:28:44 UTC

I'm working the support case similar to this BZ. If the customer hits this issue, how can they workaround?
Does removing the directory help?

# rm -rf /var/lib/origin/openshift.local.volumes/pods/xxxxxxxxxxxxxxxxxx[pod-id]

Thanks