Red Hat Bugzilla – Bug 1255015
gdeploy: unmount fails with fstype parameter
Last modified: 2016-07-03 21:12:45 EDT
Description of problem: unmount fails when fstype parameter is passed with the config file. Even though the results show the run as success, the volume continues to remain mounted on the client.
Removing the fstype parameter fixes the issue.
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 run remove-brick operations
3. Run gdeploy: gdeploy -k -c /opt/gluster.conf
gdeploy run shows as succeeded, but umount command not executed on the client.
fstype parameter should be ignored and umount should succeed.
In the config file:-
Fixed in commit https://github.com/gluster/gdeploy/commit/2a9a57a73b21909deb4e60600081385ec8491316
Will be available in next build
Verified with gdeploy-1.0-9.el7rhgs.noarch
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.