Back to bug 1318472
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Dan McPherson | 2016-03-17 11:41:24 UTC | Priority | unspecified | medium |
| Severity | unspecified | medium | ||
| Paul Morie | 2016-03-17 15:31:54 UTC | CC | knakayam, pmorie | |
| Flags | needinfo?(knakayam) | |||
| Paul Morie | 2016-03-17 21:18:37 UTC | Assignee | bchilds | pmorie |
| Paul Morie | 2016-03-17 21:18:50 UTC | Status | NEW | ASSIGNED |
| Eric Jones | 2016-03-17 22:31:56 UTC | CC | erjones | |
| Flags | needinfo?(knakayam) | |||
| Mike Barrett | 2016-03-18 02:15:38 UTC | Priority | medium | urgent |
| CC | mbarrett | |||
| Severity | medium | urgent | ||
| Andy Goldstein | 2016-03-18 16:11:32 UTC | CC | agoldste | |
| Scott Dodson | 2016-03-21 18:29:45 UTC | Status | ASSIGNED | MODIFIED |
| Fixed In Version | atomic-openshift-3.1.1.6-4.git.32.adf8ec9.el7aos | |||
| errata-xmlrpc | 2016-03-21 18:32:42 UTC | Status | MODIFIED | ON_QA |
| Scott Dodson | 2016-03-21 18:48:01 UTC | Doc Text | Cause: NFS Persistent Volumes were marked with their claim name during the mount process rather than the actual volume name. Consequence: The periodic cleanup process would unmount the volume if a pod utilizing the Persistent Volume Claim had not yet entered running state. Fix: When mounting an NFS Persistent Volumes they're now mounted with the actual volume name preventing the cleanup process from considering them orphaned. Result: NFS Persistent Volumes are no longer unmounted while the pod requiring the volume is starting. |
|
| Brenton Leanhardt | 2016-03-21 19:16:28 UTC | CC | bleanhar | |
| Andy Goldstein | 2016-03-21 19:21:27 UTC | Doc Text | Cause: NFS Persistent Volumes were marked with their claim name during the mount process rather than the actual volume name. Consequence: The periodic cleanup process would unmount the volume if a pod utilizing the Persistent Volume Claim had not yet entered running state. Fix: When mounting an NFS Persistent Volumes they're now mounted with the actual volume name preventing the cleanup process from considering them orphaned. Result: NFS Persistent Volumes are no longer unmounted while the pod requiring the volume is starting. | Cause: Persistent Volume Claims were added to the list of volumes to preserve rather than the actual name of the Persistent Volume associated with the Persistent Volume Claim. Consequence: The periodic cleanup process would unmount the volume if a pod utilizing the Persistent Volume Claim had not yet entered running state. Fix: The actual name of the Persistent Volume associated with a Persistent Volume Claim is used when determining which volumes can be cleaned up, preventing the cleanup process from considering them orphaned. Result: Persistent Volumes are no longer unmounted while the pod requiring the volume is starting. |
| Jianwei Hou | 2016-03-22 03:00:41 UTC | Keywords | NeedsTestCase | |
| Jianwei Hou | 2016-03-22 06:02:58 UTC | Status | ON_QA | VERIFIED |
| errata-xmlrpc | 2016-03-24 00:29:48 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-03-24 15:54:02 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-03-24 11:54:02 UTC | |||
| Eric Rich | 2016-03-29 20:31:43 UTC | Target Release | --- | 3.1.1 |
Back to bug 1318472