On 15-12-2015 12:31, Sahina Bose wrote:
On 12/15/2015 03:26 PM, Joop wrote:
> On 14-12-2015 12:00, Joop wrote:
>> I have reinstalled my test environment have come across an old error,
>> see BZ 988299, Bad volume specification {u'index': 0,.
>>
>> At the end of that BZ there is mentioning of a problem with '_' in the
>> name of the volume and a patch is mentioned but the code has since been
>> change quite a bit and I can't find if that still applies. It look like
>> it doesn't because I have a gluster volume with the name
>> gv_ovirt_data01
>> and it look like it gets translated to gv__ovirt__data01 and then I
>> can't start any VMs :-(
>> Weird thing, I CAN import VMs from the export domain to this gluster
>> domain.
>>
> I have just done the following on 2 servers which also hold the volumes
> with '_' in it:
>
> mkdir -p /gluster/br-ovirt-data02
>
> ssm -f create -p vg_`hostname -s` --size 10G --name lv-ovirt-data02
> --fstype xfs /gluster/br-ovirt-data02
>
> echo /dev/mapper/vg_`hostname -s`-lv-ovirt-data02
> /gluster/br-ovirt-data02 xfs defaults 1 2 >>/etc/fstab
>
> semanage fcontext -a -t glusterd_brick_t /gluster/br-ovirt-data02
>
> restorecon -Rv /gluster/br-ovirt-data02
>
> mkdir /gluster/br-ovirt-data02/gl-ovirt-data02
>
> chown -R 36:36 /gluster/
>
> Added a replicated volume on top of the above, started it, added a
> Storage Domain using that volume, moved a disk to it, and started the
> VM, works! :-)
>
> Should I open a BZ or does someone know of an existing one?
Could you open one?
I'll. Thanks.
Joop