Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1447768

Summary: [3.5] During cluster issues, node left mounts on the nodes referring to Persistent Storage, these mounts removed all the data from the PVs
Product: OpenShift Container Platform Reporter: Bradley Childs <bchilds>
Component: StorageAssignee: hchen
Status: CLOSED ERRATA QA Contact: Liang Xia <lxia>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.5.1CC: aos-bugs, eparis, hchen, jhou, lxia, vwalek, wehe
Target Milestone: ---   
Target Release: 3.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: During cluster issues, node left mounts on the nodes referring to Persistent Storage, these mounts removed all the data from the PV. Consequence: Data on the PVs are deleted. Fix: Cleaning up Pods on the nodes doesn't delete data on PVs. Result: Data on the PVs are no longer deleted during Pods cleanup.
Story Points: ---
Clone Of: 1447767 Environment:
Last Closed: 2017-06-15 18:39: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: 1447312, 1447763, 1447764, 1447765, 1447767    
Bug Blocks:    

Comment 1 Eric Paris 2017-05-11 15:54:03 UTC
https://github.com/openshift/ose/pull/730

Comment 2 Liang Xia 2017-05-24 10:56:27 UTC
Verified on v3.5.5.18

Steps:
1. Set up cluster with 1 master, 2 nodes.
2. Create NFS PV and create an app using the jenkins-persistent template.
3. Once the jenkins pod is running, bring down the node which jenkins' pod resides on by stopping it's node service.
4. The pod will be redeployed to another schedulable node(the mount path will exist on both nodes).
5. After the pod is deployed to another node, bring back the stopped node service.
6. On the original node, verify the jenkins pod volume is successfully unmounted, the pod directory is removed while all data in the persistent volume are still there.

Comment 4 Liang Xia 2017-06-05 06:39:53 UTC
According to #comment 2, move bug to verified.

Comment 6 errata-xmlrpc 2017-06-15 18:39:05 UTC
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-2017:1425