M->N upgrade causes container reboot due to bind mounts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Invalid
|
Medium
|
Unassigned |
Bug Description
The Mitaka upgrade playbooks set a default_
However the containers all reboot anyway because of a change in the bind mount syntax deployed to the lxc config for the other non-log bind mounts.
Example old entry:
lxc.mount.entry = /openstack/
another entry is appended to the lxc config for this container:
lxc.mount.entry = /openstack/
So the result is the bind mount is specified twice (once with ",create=dir" and once without) in the container config, and the change also triggers a container restart.
The old entry was managed here:
https:/
And the new one is managed here:
https:/
Typoed the first line line of the bug report, this is the NEWTON upgrade being performed.