Newton upgrade fails due to bind mount of /var/log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
High
|
Andy McCrae |
Bug Description
Recently performed an upgrade from a mid-August Newton deploy to recent master deploy. Various tasks failed due to the inability for the respective services to start inside their containers. Issues were experience with Neutron, Galera, Nova containers, among others.
The issues seems to be that the /var/log directory is now a bind mount to the host. As a result, log directories no longer exist when the container is restarted during upgrade and many services refuse to start. For some services, creating the respective log directory is enough. A more reliable method is to monkey with the mounts and copy the data from /var/log in the container to the host for presentation through the bind mount afterwards. An example of how this was done for Galera can be seen here: http://
Another user upgrading from Mitaka/stable reports the same issue during upgrade.
Changed in openstack-ansible: | |
importance: | Undecided → High |
Changed in openstack-ansible: | |
assignee: | Kevin Carter (kevin-carter) → Andy McCrae (andrew-mccrae) |
Fix proposed to branch: master /review. openstack. org/373561
Review: https:/