Bug 1281726
Summary: | NFS Recycler Fails in containerized Kubernetes | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Liang Xia <lxia> |
Component: | Storage | Assignee: | Mark Turansky <mturansk> |
Status: | CLOSED ERRATA | QA Contact: | Liang Xia <lxia> |
Severity: | medium | Docs Contact: | |
Priority: | urgent | ||
Version: | 3.1.0 | CC: | aos-bugs, bchilds, bleanhar, dmcphers, jliggitt, jokerman, lxia, mturansk, pruan |
Target Milestone: | --- | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | 1277608 | Environment: | |
Last Closed: | 2015-12-08 17:03:24 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: | 1277608 | ||
Bug Blocks: |
Comment 1
Liang Xia
2015-11-13 10:06:44 UTC
# oc describe pv nfs Name: nfs Labels: <none> Status: Failed Claim: default/nfsc Reclaim Policy: Recycle Access Modes: RWO Capacity: 5Gi Message: Recycling error: Pod was active on the node longer than specified deadline Source: Type: NFS (an NFS mount that lasts the lifetime of a pod) Server: *(Server info hide here) Path: /jhou ReadOnly: false Mark the bug as regression since we suspect it is caused by https://github.com/openshift/origin/pull/5847 @liang Xia, What is the timeout on the pod? when the PV is being recycled, you can view the recycler pod with "oc get pod". If the pod is timing out, there should be plenty of time to see it in the API and describe it. The pod *should* have a timeout that is incremented per Gi of size. We can increase this number if it is too small currently. what are the permissions on the NFS export? PV can be recycled when NFS exported with 777. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2015:2580 |