From acaebf83ce4eddfb5d53af1ea4c3156f52738c2a Mon Sep 17 00:00:00 2001 From: Vladislav Belogrudov Date: Wed, 25 Jul 2018 17:34:43 +0300 Subject: [PATCH] Save targetcli configuration to a volume for container upgrades When using lioadm / targetcli to serve LVM volumes to instances the former saves target configuration under /etc/target. If cinder_volume container is upgraded / replaced then all targets are gone and instances cannot connect to their volumes any longer. This fix introduces target_config volume where corresponding information is persisted. Change-Id: I919bbe00853266037dd5c015810cc13c25e2e033 Closes-Bug: #1783569 --- ansible/roles/cinder/defaults/main.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/ansible/roles/cinder/defaults/main.yml b/ansible/roles/cinder/defaults/main.yml index 9725988db2..b56f59c3a9 100644 --- a/ansible/roles/cinder/defaults/main.yml +++ b/ansible/roles/cinder/defaults/main.yml @@ -37,6 +37,7 @@ cinder_services: - "/run/:/run/:shared" - "cinder:/var/lib/cinder" - "{% if enable_iscsid | bool %}iscsi_info:/etc/iscsi{% endif %}" + - "{% if enable_cinder_backend_lvm | bool and cinder_iscsi_helper == 'lioadm' %}target_config:/etc/target{% endif %}" - "kolla_logs:/var/log/kolla/" - "{{ kolla_dev_repos_directory ~ '/cinder/cinder:/var/lib/kolla/venv/lib/python2.7/site-packages/cinder' if cinder_dev_mode | bool else '' }}" cinder-backup: