<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/docker/nova/nova-base/nova_sudoers, branch train-eol</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla.git/atom?h=train-eol</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla.git/atom?h=train-eol'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/'/>
<updated>2016-01-20T16:58:01+00:00</updated>
<entry>
<title>Fix permissions to /var/lib/nova/</title>
<updated>2016-01-20T16:58:01+00:00</updated>
<author>
<name>Artur Zarzycki</name>
<email>azarzycki@mirantis.com</email>
</author>
<published>2016-01-13T16:28:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=ef971bff5135b88e3451eb451418327e672f6d8b'/>
<id>urn:sha1:ef971bff5135b88e3451eb451418327e672f6d8b</id>
<content type='text'>
Due to changes with the drop-root work, we lost the ability to write
to /var/lib/nova/*. This fixes those permissions and ensures cross
container talk works properly between nova_libvirt and nova_compute

Additionally, this fixes another issue introduced which saw that
nova-compute could not run sudo commands as it did not have a proper
sudoers entry

Testing from previous deploys means you need a fresh environment. You
have to remove all of the named volumes that kolla created in docker.
Check these with `docker volume ls`

Signed-off-by: Hui Kang &lt;kangh@us.ibm.com&gt;
Signed-off-by: Artur Zarzycki &lt;azarzycki@mirantis.com&gt;
Co-Authored-By: Sam Yaple &lt;sam@yaple.net&gt;
Co-Authored-By: Hui Kang &lt;kangh@us.ibm.com&gt;
Closes-Bug: #1533350
Change-Id: I7f864c448a2414e0b5d89f48337be411b891df35
</content>
</entry>
</feed>
