Bug 1242128

Summary: Deleting a volume should delete also fstab entry
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Stanislav Graf <sgraf>
Component: rhscAssignee: Sahina Bose <sabose>
Status: CLOSED CANTFIX QA Contact: RHS-C QE <rhsc-qe-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rhgs-3.1CC: asriram, knarra, nlevinki, rhs-bugs, sankarshan
Target Milestone: ---Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
Deleting a gluster volume does not remove the /etc/fstab entries for the bricks. A RHEL-7 system may fail to boot if the mount fails for any entry in the /etc/fstab file. If the LVs corresponding to the bricks are deleted but not the respective entry in /etc/fstab, then the system may not boot. Workaround: 1. Ensure that /etc/fstab entries are removed when the LVs are deleted from system. 2. If the system fails to boot, start it in emergency mode, use your root password, remount '/' in rw, edit fstab, save, and then reboot.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-30 11:39:48 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: 1216951    

Description Stanislav Graf 2015-07-11 08:06:49 UTC 
Description of problem:
=======================

Deleting a volume in RHSC should also delete (or comment out) it's entry in /etc/fstab. At the moment extra entry in /etc/fstab breaks ability of RHEL7 to boot. One needs to start in emergency mode, give root password, remount '/' in rw, edit fstab, save and reboot to fix the situation.

rhsc-3.1.0-0.62.el6.noarch
Comment 3 monti lawrence 2015-07-22 21:20:12 UTC 
Doc text is edited. Please sign off to be included in Known Issues.
Comment 4 Ramesh N 2015-07-24 11:06:43 UTC 
doc text looks good. Approved.
Comment 6 Sahina Bose 2018-01-30 11:39:48 UTC 
Thank you for your bug report. However, this bug is being closed as it's on a component where no further new development is being undertaken.