Bug 1383418 - The pv-recycler-nfs leaves the persistent volumes in Released state
Summary: The pv-recycler-nfs leaves the persistent volumes in Released state
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 3.2.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: hchen
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-10 14:48 UTC by Miheer Salunke
Modified: 2019-12-16 07:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-26 16:54:07 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Miheer Salunke 2016-10-10 14:48:00 UTC 
Description of problem:

The persistent volumes remains in the "Released" state, the pv-recycler-nfs process can not release and put them to "Available" state, but the persistent volume claims are deleted.

We have two infra nodes, some pods are running on the second one and no pods are on the first one.
The pv-recycler-nfs pods try to run on the first one, but without success.



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

How reproducible:

On customer side

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 5 hchen 2016-10-11 12:55:36 UTC 
probably fixed in openshift 3.3 (kubernetes 1.3).
Note You need to log in before you can comment on or make changes to this bug.