This reverts commit 43650d5837372449294a7a22e9c9167a92744e96.
This fix do not work with CentOS x86_64. Since I haven't arm64 env, and
we have fix this soon before pike is release. Just revert this and fix
in the future.
Change-Id: Id9eb531de7d05051f38e3ed13b64ae7abf552767
Partial-Bug: #1715356
When deploying on arm64, permission denied reported:
Terminating instance: libvirtError: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied
Fix the issue via "chown root:kvm /dev/kvm"
Change-Id: Ib963741918b47d924ca0716643ac14a3fc3cfab2
Signed-off-by: Kevin Zhao <kevin.zhao@linaro.org>
Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
This centralizes all user and group creation into a single source. This
will fix any current and furture uid/gid mismatches (such as with
nova-libvirt).
In the process, we also unify users between the distros in a standard
way. The users in the following containers change from thier defaults:
Ubuntu: _chrony user is now chrony
Ubuntu: memcache user is now memcached
All: qemu user is used for ownership and socket permissions
All uid and gid numbers are customizable via kolla-build.conf
Co-Authored-By: Kris Lindgren <klindgren@godaddy.com>
Change-Id: I120f26ab0683dc87d69727c3df8d4707e52a4543
Partially-Implements: blueprint static-uid-gid
Fixing permissions so all users could access libvirtd.log
Change-Id: I6f63a847ba9c5591a87922d3b117b101100b2fad
Closes-Bug: 1563430
Co-Authored-By: Steven Dake <stdake@cisco.com>
The majority of the start.sh code is identical. This removes that
duplicate code while still maintaining the ability to call code in a
specific container.
The start.sh is moved into /usr/local/bin/kolla_start in the container
The extend_start.sh script is called by the kolla_start script at the
location /usr/local/bin/kolla_extend_start . It always exists because
we create a noop kolla_extend_start in the base directory. We override
it with extend_start.sh in a specific image should we need to.
Of note, the neutron-agents container is exempt from this new
structure due to it being a fat container.
Additionally, we fix the inconsistent permissions throughout. 644 for
repo files and the scripts are set to 755 via a Docker RUN command to
ensure someones local perm change won't break upstream containers.
Change-Id: I7da8d19965463ad30ee522a71183e3f092e0d6ad
Closes-Bug: #1501295