Bug 1447312
Summary: | [3.3] 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: | Vladislav Walek <vwalek> | |
Component: | Storage | Assignee: | hchen | |
Status: | CLOSED ERRATA | QA Contact: | Wenqi He <wehe> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 3.3.0 | CC: | aos-bugs, bchilds, eparis | |
Target Milestone: | --- | |||
Target Release: | 3.3.1 | |||
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: | ||||
: | 1447763 (view as bug list) | Environment: | ||
Last Closed: | 2017-06-15 18:38:21 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: | ||||
Bug Blocks: | 1447763, 1447764, 1447765, 1447767, 1447768 |
Description
Vladislav Walek
2017-05-02 12:10:33 UTC
*** Bug 1447765 has been marked as a duplicate of this bug. *** Verified on v3.3.1.28 Steps: 1. Create NFS PV and create an app using the jenkins-persistent template. 2. Once the jenkins pod is running, bring down the node by stopping it's node service. 3. The pod will be redeployed to another schedulable node. 4. After the pod is deployed to another node, bring back the stopped node service. 5. 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. 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 |