Bug 1254991 - gdeploy: unmount doesn't remove fstab entries
Summary: gdeploy: unmount doesn't remove fstab entries
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gdeploy
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: RHGS 3.1.1
Assignee: Nandaja Varma
QA Contact: Anush Shetty
URL:
Whiteboard:
Depends On:
Blocks: 1251815
TreeView+ depends on / blocked
 
Reported: 2015-08-19 11:56 UTC by Anush Shetty
Modified: 2019-11-14 10:46 UTC (History)
4 users (show)

Fixed In Version: gdeploy-1.0-7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-05 07:24:05 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1845 0 normal SHIPPED_LIVE Moderate: Red Hat Gluster Storage 3.1 update 2015-10-05 11:06:22 UTC

Description Anush Shetty 2015-08-19 11:56:54 UTC 
Description of problem: Unmounting through gdeploy doesn't remove the mount entry from /etc/fstab

Version-Release number of selected component (if applicable): 1.1


How reproducible: Always

Steps to Reproduce:
1. Install gdeploy (http://file.india.redhat.com/surs/gdeploy/gdeploy-1-1.noarch.rpm)
2. Edit the config file to add mount details
3. Run gdeploy: gdeploy -k -c /opt/gluster.conf


Additional info:

gdeploy config file:-

[volume]
action=remove-brick                                                             volname=glustervol2

[clients]
action=unmount
hosts=rhshdp03.lab.eng.blr.redhat.com
client_mount_points=/mnt/gluster6
Comment 2 Nandaja Varma 2015-08-19 12:10:25 UTC 
Fixed and updated the code in github. Fix will be available with the next build.
Comment 3 Anush Shetty 2015-09-08 09:38:55 UTC 
Verified with gdeploy-1.0-9.el7rhgs.noarch
Comment 6 errata-xmlrpc 2015-10-05 07:24: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://rhn.redhat.com/errata/RHSA-2015-1845.html
Note You need to log in before you can comment on or make changes to this bug.