openstack/kolla
Code Issues Proposed changes
dd821c132c
kolla/docker/nova/nova-compute/extend_start.sh

6 lines
97 B
Bash
Raw Normal View History

Fix permissions to /var/lib/nova/ 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 <kangh@us.ibm.com> Signed-off-by: Artur Zarzycki <azarzycki@mirantis.com> Co-Authored-By: Sam Yaple <sam@yaple.net> Co-Authored-By: Hui Kang <kangh@us.ibm.com> Closes-Bug: #1533350 Change-Id: I7f864c448a2414e0b5d89f48337be411b891df35
2016-01-13 17:28:53 +01:00
#!/bin/bash
Create the nova instances directory when need during starting The /var/lib/nova/instances should be create if it do not exist during starting nova-compute container. Rather than create it at the bootstrap service stage. Change-Id: Ibcc5fb8eec0b38cf2b4313f48d1beb3ba83b1e85 Closes-Bug: #1614970
2016-08-19 21:54:28 +08:00
if [[ ! -d /var/lib/nova/instances ]]; then
Safely create directories This prevents failure when the directory already exists. This commit fixes a failure in centos-binary because of a change in the RDO packaging, where the required directory is now created for us. Change-Id: Idd3e15802c3e3fd363e1295111ec12948d566781 Closes-Bug: #1543417
2016-02-09 14:07:53 +09:00
mkdir -p /var/lib/nova/instances
Fix permissions to /var/lib/nova/ 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 <kangh@us.ibm.com> Signed-off-by: Artur Zarzycki <azarzycki@mirantis.com> Co-Authored-By: Sam Yaple <sam@yaple.net> Co-Authored-By: Hui Kang <kangh@us.ibm.com> Closes-Bug: #1533350 Change-Id: I7f864c448a2414e0b5d89f48337be411b891df35
2016-01-13 17:28:53 +01:00
fi
Copy Permalink