commit 1d4c3ad6ece7648d7329c5a6bfd42ed9b53b3022
Author: Paulo Matias <email address hidden>
Date: Thu Oct 27 17:24:50 2016 -0200
Fix permissions for the Nova lock directory in systemd
The directory set as `lock_path` in `nova.conf` must be created with
the nova system user as its owner, otherwise the VIF plugin would fail
to acquire a lock when launching an instance.
Here we set up systemd to create this directory with correct owner and
permissions, besides moving its path to a `nova_lock_path` variable.
Apparently, the `/var/lock/{{ item.value.service_name }}` directory,
which is also created by `nova-systemd-tempfiles.j2`, is not needed at
all. But as this patch is intended to be backported to a stable release,
we keep it by now to avoid any unforeseen issues.
Reviewed: https:/ /review. openstack. org/391295 /git.openstack. org/cgit/ openstack/ openstack- ansible- os_nova/ commit/ ?id=1d4c3ad6ece 7648d7329c5a6bf d42ed9b53b3022
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1d4c3ad6ece7648 d7329c5a6bfd42e d9b53b3022
Author: Paulo Matias <email address hidden>
Date: Thu Oct 27 17:24:50 2016 -0200
Fix permissions for the Nova lock directory in systemd
The directory set as `lock_path` in `nova.conf` must be created with
the nova system user as its owner, otherwise the VIF plugin would fail
to acquire a lock when launching an instance.
Here we set up systemd to create this directory with correct owner and
permissions, besides moving its path to a `nova_lock_path` variable.
Apparently, the `/var/lock/{{ item.value. service_ name }}` directory, tempfiles. j2`, is not needed at
which is also created by `nova-systemd-
all. But as this patch is intended to be backported to a stable release,
we keep it by now to avoid any unforeseen issues.
Change-Id: I9886778eddc23f 0f71dfdfc87f4f7 15054946b3d
Closes-Bug: #1636604