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.
I'm running from devstack setup - so I don't have an init-script. All the
processes run in a screen session.
Here is what I did :
1. Stopped nova-compute
Ø Check if not only root can write on the nfs share (specially libvirt user).
It doesn’t look like permissions issue to me. Just to be doubly sure, I
“touched” a file, in that folder, edited and deleted the file. All operations
worked w/o error.
As I have listed below, several files got
unchpad.net" openstack@lists.launchpad.netSubject: Re: [Openstack] 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.I'm running from devstack setu
03, 2012 10:14 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] Instance fails to spawn when instance_path is nfs mounted
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
stack@lists.launchpad.net" openstack@lists.launchpad.netSubject: Re: [Openstack] Instance fails to spawn when instance_path is nfs mountedØ
Check if not only root can write on the nfs share (specially libvirt user).It doesn’t look like permissions issue to me. Just to be d
!!!
Thanks Rohit !!!
Thanks Vish !!
-Mandar
From: Vaze, Mandar
Sent: Wednesday, April 04, 2012 4:41 PM
To: openstack@lists.launchpad.net
Cc: 'vishvana...@gmail.com'
Subject: RE: [Openstack] Instance fails to spawn when instance_path is nfs
mounted
All,
On the link given below vish asked if I
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
http://www.stackops.com/*CEO*
*www.stackops.com | *
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.santama...@gmail.com wrote:
We use nfs backed instances a lot, and this problem
8 matches
Mail list logo
