Red Hat Bugzilla – Bug 1182369
[RFE][HC] - glusterfs volume create/extend should fail when bricks from the same server
Last modified: 2017-02-15 10:07:05 EST
Description of problem: Although the UI warns when creating a replica set containing bricks from the same server - it should actually fail the request when the nodes are gluster and virt i.e. hyper-converged, Version-Release number of selected component (if applicable): 3.5 How reproducible: n/a Steps to Reproduce: 1. create a replicated volume by providing all bricks from the same node 2. UI provides a warning (Replicate Confirmation dialog) which the user can ignore 3. Actual results: Volume can be created Expected results: Volume made from multiple bricks from the same server in a converged use case represents a data loss or service loss risk. The UI should enforce sensible decisions to safeguard service availability. Additional info:
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Bricks from same server in a replica set should be blocked
Moving from 4.0 alpha to 4.0 beta since 4.0 alpha has been already released and bug is not ON_QA.
oVirt 4.0 beta has been released, moving to RC milestone.
Hi Sahina Can you please confirm whether this chapter of the Administration Guide will need to be updated to support this new behaviour: https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/administration-guide/#sect-Cluster_Utilization If not, should it be documented anywhere else?
Doc-text looks good to me. The "Global Inventory" needs to be updated, but as part of Bug 1364999
Tested with RHV 4.1 Beta ( Red Hat Virtualization Manager Version: 4.1.0.3-0.1.el7 ) When trying to create a gluster replica 3 volume with bricks on the same server, the operation failed with following error message: "Error while executing action: Cannot create Gluster Volume. Replica set contains bricks from same server. This is not supported for hyper-converged cluster."
So in a cluster with 4 nodes, the only way to create a replica 3/arbiter 1 volume is with 12 bricks, 3 on each node. Is this now going to be impossible?