openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #09523
Re: Instance fails to spawn when instance_path is nfs mounted
I had a problem like this when the umask was locked down. Setting the
umask to 022 in the init script for nova-compute solved my problem.
On Tue, Apr 3, 2012 at 1:56 PM, Diego Parrilla Santamaría
<diego.parrilla.santamaria@xxxxxxxxx> wrote:
> We use nfs backed instances a lot, and this problem normally has to do with
> wrong permission management in your filer and/or client.
>
> Check if not only root can write on the nfs share (specially libvirt user).
>
> Diego
> --
> Diego Parrilla
> CEO
> www.stackops.com | diego.parrilla@xxxxxxxxxxxx | +34 649 94 43 29
> | skype:diegoparrilla
>
>
>
>
> On Tue, Apr 3, 2012 at 6:43 PM, Mandar Vaze / मंदार वझे
> <mandarvaze@xxxxxxxxx> wrote:
>>
>> I saw an old question posted here :
>> https://answers.launchpad.net/nova/+question/164689
>>
>> But I am not trying live migration.
>>
>> I have nfs mounted instances_path - so when I try to spawn an instance I
>> run into the above errors. Especially following :
>>
>> File "/usr/lib/python2.7/dist-packages/libvirt.py", line 372, in
>> createWithFlags
>> 40842 2012-04-03 05:42:27 TRACE nova.rpc.amqp if ret == -1: raise
>> libvirtError ('virDomainCreateWithFlags() failed', dom=self)
>> 40843 2012-04-03 05:42:27 TRACE nova.rpc.amqp libvirtError: internal error
>> Process exited while reading console log output: chardev: opening
>> backend "file" failed
>>
>> But as you can see below, several files are created in this folder, so I
>> am not sure if mine if permissions issue (Else none of the files would
>> get created) The problem is reported when libvirt tries to write to
>> console.log (File itself is created with correct permissions - just that
>> this is zero byte file)
>>
>> mandar@ubuntu-dev-mandar:/nfs_shared_instances_path/instance-00000005$ ll
>> total 10944
>> drwxrwxr-x 2 mandar libvirtd 4096 2012-04-03 05:42 ./
>> drwxrwxrwx 4 root root 4096 2012-04-03 05:42 ../
>> -rw-rw---- 1 mandar libvirtd 0 2012-04-03 05:42 console.log
>> -rw-r--r-- 1 mandar libvirtd 6291968 2012-04-03 05:42 disk
>> -rw-rw-r-- 1 mandar libvirtd 4731440 2012-04-03 05:42 kernel
>> -rw-rw-r-- 1 mandar libvirtd 1067 2012-04-03 05:42 libvirt.xml
>> -rw-rw-r-- 1 mandar libvirtd 2254249 2012-04-03 05:42 ramdisk
>>
>> I'm suspecting :
>> https://bugs.launchpad.net/ubuntu/maverick/+source/libvirt/+bug/632696
>> But I the above doesn't show itself in non-NFS setup
>>
>> Please suggest !!!
>>
>> -Mandar
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
>>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
Follow ups
References