VDSM is not supporting anymore deploying gluster storage with only 1 brick. Traceback (most recent call last): File "/usr/share/vdsm/storage/hsm.py", line 2461, in connectStorageServer conObj.connect() File "/usr/share/vdsm/storage/storageServer.py", line 213, in connect self.validate() File "/usr/share/vdsm/storage/storageServer.py", line 313, in validate raise se.UnsupportedGlusterVolumeReplicaCountError(replicaCount) UnsupportedGlusterVolumeReplicaCountError: Gluster volume replica count is not supported: 'replica count = 1' so moving to replica 3 deployment is now mandatory.
After discussing this with Nir, Allon and Yaniv, moving to VDSM. Single brick on a single host in HC configuration must be allowed as it should be allowed to grow to replica 3 in a second step.
This is actually an intentional changed introduced for bug 1123052. For a quick relief, a manual step for overriding this is to edit /etc/vdsm/vdsm.conf, uncomment allowed_replica_counts and set it to "allowed_replica_counts=1,3". For a "real" solution, we need to think about this, but perhaps the installer could enable the conf value just to get things running
*** Bug 1243323 has been marked as a duplicate of this bug. ***
(In reply to Allon Mureinik from comment #2) > This is actually an intentional changed introduced for bug 1123052. > > For a quick relief, a manual step for overriding this is to edit > /etc/vdsm/vdsm.conf, uncomment allowed_replica_counts and set it to > "allowed_replica_counts=1,3". > > For a "real" solution, we need to think about this, but perhaps the > installer could enable the conf value just to get things running Discussed with Yaniv Dary - Replica 1 is important to existing users, we'll return the built-in support for it (see attached patch).
was this backported to 3.6? Can you attach the patch?
(In reply to Yaniv Dary from comment #5) > was this backported to 3.6? No need to, the patch referenced in the external tracker was commited to master before the ovirt-3.6 branch was forked from it: amureini@dhcp-0-202 ~/src/git/vdsm [ovirt-3.6] $ git branch --contains c9e52d070f5414d39d53499f61fa51218543c023 master * ovirt-3.6
Let's handle the doctext in one place - bug 1238093. I'm flagging this BZ with requires-doctext-.
This bug report has Keywords: Regression or TestBlocker. Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Verified on rhevm-3.6.0.3-0.1.el6.noarch Volume: # gluster volume info test_for_bug Volume Name: test_for_bug Type: Distribute Volume ID: 8a364ff5-f016-4bff-b373-06a9bc1ae37e Status: Started Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.35.160.202:/gluster_volumes/test_for_bug Options Reconfigured: performance.readdir-ahead: on On vdsm: # mount | grep 10.35.160.202 10.35.160.202:/test_for_bug on /rhev/data-center/mnt/glusterSD/10.35.160.202:_test__for__bug type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072) The storage domain created successfully
Since oVirt 3.6.0 has been released, moving from verified to closed current release.