Red Hat Bugzilla – Bug 1051696
Unable to create a volume with bricks in the root partition for 3.2 clusters made up of 3.1u2 nodes
Last modified: 2016-04-18 06:06:41 EDT
Description of problem: On a 3.2 cluster with 2.1u2 nodes added, an error message is given when a user tries to create a volume with bricks in the root partition. The error message implies that there is a force option which isn't present; from the gui there is no way to create a volume with bricks in the root partition in a 3.2 cluster made up of 2.1u2 nodes. This is also inconsistent behavior when compared to 3.2 clusters made up of 2.1 and 3.2 clusters made up of 2.1u1 nodes. In these type of clusters, the cluster creates volumes successfully even when bricks are in the root partition. Version-Release number of selected component (if applicable): rhsc-cb14 How reproducible: 100% Steps to Reproduce: 1. create a 3.2 cluster 2. add 2 2.1u2 nodes to the cluster 3. create a volume using bricks in the root partition for example /tmp/brick1 Actual results: error message is prompted to user "Error while executing action Create Gluster Volume: Volume create failed error: The brick vm10_lab_eng_blr_redhat_com:/home/test is is being created in the root partition_ It is recommended that you don't use the system's root partition for storage backend_ Or use 'force' at the end of the command if you want to override this behavior_ return code: 115" user is unable to create a volume with bricks in the root partition Expected results: rhsc should allow creation of bricks in the root partition without prompting to be consistent with 3.2 clusters of 2.1 nodes and 3.2 clusters of 2.1u1 nodes. Additional info:
VDSM in RHS-2.1-U2(Corbett) has 3.3 Compatibility Version and VDSM in RHS-2.1(Bigbend and U1) has 3.2 Compatibility Version. RHS-2.1 and U1 nodes doesn't support 'force' option in 'volume create' and 'add-bricks' commands, also allow bricks in root partition. If someone is trying to add a node to a 3.2 Cluster, engine identifies that node as 3.2 compatible and allow the operations which are supported for 3.2 cluster. 'Force' option is a 3.3 cluster operation, which can not be performed on a 3.2 cluster. This is the reason why 'force' option is not shown in the UI. Even though user is adding a node which has higher compatibility version(ex: 3.3) than the cluster(ex:3.2) which it belongs to, only the operations supported for the compatibility version(3.2) of the cluster is allowed .
Hi Kanagaraj, I agree with you that the force option should not be available in 3.2 clusters. However, the behavior seen is different depending on what nodes you use in the 3.2 cluster. For example following the steps below using different nodes yields diff results.... 1. create a 3.2 cluster 2. add 2 nodes to the cluster 3. create a volume using bricks in the root partition for example /tmp/brick1 with 2.1u1 and 2.1: volume is created successfully with 2.1u2 nodes: "Error while executing action Create Gluster Volume: Volume create failed error: The brick vm10_lab_eng_blr_redhat_com:/home/test is is being created in the root partition_ It is recommended that you don't use the system's root partition for storage backend_ Or use 'force' at the end of the command if you want to override this behavior_ return code: 115"
The cluster version and node version compatibility and how it would behave has to be documented in the Admin guide.
Please review the edited Doc Text and sign off.
small change in the workaround "Do not create", rest looks good
Bricks in root partition is not recommended, and work-around exists if needed.