openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #01979
Nova writing lock files in /usr/lib/pymodules/python2.6
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)
Follow ups