On Wed, Jul 5, 2017 at 7:42 AM, Sahina Bose <sabose@redhat.com> wrote:

...

then the commands I need to run would be:

gluster volume reset-brick export ovirt01.localdomain.local:/gluster/brick3/export start
gluster volume reset-brick export ovirt01.localdomain.local:/gluster/brick3/export gl01.localdomain.local:/gluster/brick3/export commit force

Correct?

Yes, correct. gl01.localdomain.local should resolve correctly on all 3 nodes.

It fails at first step:

 [root@ovirt01 ~]# gluster volume reset-brick export ovirt01.localdomain.local:/gluster/brick3/export start

volume reset-brick: failed: Cannot execute command. The cluster is operating at version 30712. reset-brick command reset-brick start is unavailable in this version.

[root@ovirt01 ~]# 

It seems somehow in relation with this upgrade not of the commercial solution Red Hat Gluster Storage

https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Installation_Guide/chap-Upgrading_Red_Hat_Storage.html

So ti seems I have to run some command of type:

gluster volume set all cluster.op-version XXXXX

with XXXXX > 30712

It seems that latest version of commercial Red Hat Gluster Storage is 3.1 and its op-version is indeed 30712..

So the question is which particular op-version I have to set and if the command can be set online without generating disruption....

Thanks,

Gianluca