[Users] unable to start vm in 3.3 and f19 with gluster

[David Riedl]

On 25.09.2013 09:11, Vijay Bellur wrote:
> On 09/25/2013 11:51 AM, Gianluca Cecchi wrote:
>> On Wed, Sep 25, 2013 at 8:11 AM, Vijay Bellur  wrote:
>>
>>>
>>>
>>> Have the following configuration changes been done?
>>>
>>> 1) gluster volume set <volname> server.allow-insecure on
>>>
>>> 2) Edit /etc/glusterfs/glusterd.vol on all gluster nodes to contain 
>>> this
>>> line:
>>>              option rpc-auth-allow-insecure on
>>>
>>> Post 2), restarting glusterd would be necessary.
>>>
>>> Regards,
>>> Vijay
>>
>>
>> No, because I didn't find find this kind of info anywhere... ;-)
>
> The feature page wiki does provide this information but it gets missed 
> in the details. Should we highlight it more?
>
>>
>> Done on both hosts (step 1 only one time) and I see that the gui
>> detects the change in volume setting.
>> Now the VM can start (I see the qemu process on ovnode02) but it seems
>> to remain in hourglass state icon.....
>> After 5 minutes it still remains in "executing" phase in tasks
>>
>
> Let us know how this goes.
>
> -Vijay
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users

I found a bug report on your issue.
https://bugzilla.redhat.com/show_bug.cgi?id=988299

Scroll to the end. ( 
https://bugzilla.redhat.com/show_bug.cgi?id=988299#c46 )
There is a modified glusterVolume.py. I have the same issue as well, I'm 
trying to fix this it right now.

Regards David

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20130926/4fe80204/attachment-0001.html>