openstack team mailing list archive

[Diego Parrilla Santamaría <diego.parrilla.santamaria@xxxxxxxxx>]

I have found some random issues if you don't set the lock_path to a
writeable directory in Cactus. Never saw any issue in Bexar. Hence, in
the new version of our distro the lock_path parameter is always set.

-- 
Diego Parrilla
CEO
www.stackops.com |  diego.parrilla@xxxxxxxxxxxx | +34 649 94 43 29 |
skype:diegoparrilla



On Wed, Apr 27, 2011 at 4:40 AM, Thomas Goirand <thomas@xxxxxxxxxx> wrote:
> Hi,
>
> I thought I was the only one, as using Debian, but it seems I'm not.
>
> Nova is trying to write in /usr/lib/pymodules/python2.6. It should not,
> as an admin can decide to mount /usr read only. Here's the output:
>
> http://paste.openstack.org/show/1253/
>
> Of course, doing:
>
> chown nova /usr/lib/pymodules/python2.6
>
> kinds of fixes it, but that should never happens. Lock files should be
> written somewhere in /var, probably in /var/lib/nova/locks in this case.
>
> Is this a known issue (I haven't see it in a launchpad bug)? Is that an
> issue in python-lockfile? And more importantly: how to fix?
>
> I saw, in utils.py, a "FLAGS.lock_path". Should I just add a
> --lock_path=/var/lib/nova/locks in /etc/nova/nova.conf? In this case,
> why isn't /var/lib/nova/locks the default, and how to change that
> default in the code so that by default it goes in /var?
>
> Thomas Goirand (zigo)
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>