M->N upgrade causes container reboot due to bind mounts

Bug #1665084 reported by Logan V on 2017-02-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

The Mitaka upgrade playbooks set a default_bind_mount_logs: false entry to prevent a reboot of all the containers due to the log bind mount change.

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/lsn-d6045_galera_container-174f0faa var/lib/mysql none bind 0 0

another entry is appended to the lxc config for this container:
lxc.mount.entry = /openstack/lsn-d6045_galera_container-174f0faa var/lib/mysql none bind,create=dir 0 0

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:

And the new one is managed here:

Logan V (loganv) wrote :

Typoed the first line line of the bug report, this is the NEWTON upgrade being performed.

Logan V (loganv) wrote :

Looks like this affects the following playbooks:

playbooks/os-neutron-install.yml: - "lxc.mount.entry=/lib/modules lib/modules none bind 0 0"
playbooks/os-glance-install.yml: - "lxc.mount.entry=/openstack/{{ container_name }} var/lib/glance/images none bind 0 0"
playbooks/repo-server.yml: - "lxc.mount.entry=/openstack/{{ container_name }} var/www none bind 0 0"
playbooks/galera-install.yml: - "lxc.mount.entry=/openstack/{{ container_name }} var/lib/mysql none bind 0 0"

Adding a regexp to the lineinfile would avoid the duplicate lines, while the serialization here: https://review.openstack.org/#/c/426928/ would avoid the mess of the massive restart.

Changed in openstack-ansible:
status: New → Confirmed
tags: added: low-hanging-fruit
Changed in openstack-ansible:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers