Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1257162 - gdeploy: volume force option doesn't work as expected
gdeploy: volume force option doesn't work as expected
Status: CLOSED ERRATA
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gdeploy (Show other bugs)
3.1
Unspecified Unspecified
unspecified Severity unspecified
: ---
: RHGS 3.1.1
Assigned To: Nandaja Varma
Anush Shetty
: ZStream
Depends On:
Blocks: 1251815
  Show dependency treegraph
 
Reported: 2015-08-26 07:57 EDT by Anush Shetty
Modified: 2016-07-03 21:12 EDT (History)
4 users (show)

See Also:
Fixed In Version: gdeploy-1.0-11
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-05 03:24:45 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1845 normal SHIPPED_LIVE Moderate: Red Hat Gluster Storage 3.1 update 2015-10-05 07:06:22 EDT

  None (edit)
Description Anush Shetty 2015-08-26 07:57:24 EDT
Description of problem: The force option under Volume in gdeploy config file doesn't fail volume creation fail when the bricks are created over root partition or when the brick sizes are uneven.

Version-Release number of selected component (if applicable): gdeploy-1.0-6.el7rhgs.noarch.rpm


How reproducible: Always


Steps to Reproduce:
1. Install deploy: https://brewweb.devel.redhat.com/buildinfo?buildID=453652
2. Create config file enabling volume creation with "force=no" and bricks of unequal sizes. 
3. Run gdeploy

Actual results:

Volume creation succeeds

Expected results:

1) The force option under Volume in gdeploy config file is expected work like the force option in gluster cli. It is expected to issue a warning and exit.

2) The default value for force should a "no"

Additional info:
Comment 2 Nandaja Varma 2015-08-26 08:57:02 EDT
Fix has been merged in the upstream branch 1.0. Will be available with next build.
Comment 3 Anush Shetty 2015-09-09 08:05:33 EDT
Even when [mountpoints] and [brick_dirs] values are given, with force=no, I get the following error:

# gdeploy -k -c gluster.conf

Error: Mountpoints cannot be brick directories.
 Provide 'brick_dirs' option/section or use force=yes in your configuration file. Exiting!
Comment 5 Anush Shetty 2015-09-14 08:17:43 EDT
Verified with gdeploy-1.0-11.el6rhs.noarch
Comment 7 errata-xmlrpc 2015-10-05 03:24:45 EDT
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.