| 2020-09-14 13:33:15 |
Jocelyn Thode |
description |
Hi,
While deploying openstack with openstack-ansible 20.1.3 (stable/train) in lxc containers we ran into an issue related to logs mount points
By default when creating the containers, the role will add a bind mount so that the journald logs are sent to the host which is very useful for log collection. (see https://github.com/openstack/openstack-ansible-lxc_container_create/blob/stable/train/tasks/lxc_container_config.yml#L44)
However, this mount point is overshadowed when running a service install after having created the containers. For example running the playbook os-heat-install.yml will overshadow the mount point /var/log/journal/... due to the variable lxc_default_bind_mounts (see https://github.com/openstack/openstack-ansible/blob/master/playbooks/common-tasks/os-lxc-container-setup.yml#L49)
Expected behavior would be that the more specific mount point would be mounted after the more general one to avoid overshadowing. |
Hi,
While deploying openstack with openstack-ansible 20.1.3 (stable/train) in lxc containers we ran into an issue related to logs mount points
By default when creating the containers, the role will add a bind mount so that the journald logs are sent to the host which is very useful for log collection. (see https://github.com/openstack/openstack-ansible-lxc_container_create/blob/stable/train/tasks/lxc_container_config.yml#L44)
However, this mount point is overshadowed when running a service install after having created the containers. For example running the playbook os-heat-install.yml will overshadow the mount point /var/log/journal/... due to the variable lxc_default_bind_mounts (see https://github.com/openstack/openstack-ansible/blob/stable/train/playbooks/common-tasks/os-lxc-container-setup.yml#L49)
Expected behavior would be that the more specific mount point would be mounted after the more general one to avoid overshadowing. |
|
