Fix docker-devicemapper playbook
Backport: train
Commit efb8b8bd27
introduced in Train uses
docker_storage_driver in a Kayobe top-level playbook, but this variable
was only defined in defaults of the docker-devicemapper role. Unless
docker_storage_driver is explicitly set by the operator, the
docker-devicemapper playbook would fail due to the variable being
undefined.
Change-Id: I5e8219d1807b1a4e3ec65f5478eb3f1c7c02b241
Story: 2007719
Task: 39857
This commit is contained in:
parent
436a28b9c8
commit
4ba18116ff
@ -2,6 +2,9 @@
|
||||
###############################################################################
|
||||
# Docker configuration.
|
||||
|
||||
# Name of the docker storage driver. Default is 'devicemapper'.
|
||||
docker_storage_driver: devicemapper
|
||||
|
||||
# Name of the docker storage LVM volume group.
|
||||
docker_storage_volume_group: data
|
||||
|
||||
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixes failure to configure Docker devicemapper storage when the default
|
||||
value of ``docker_storage_driver`` is used.
|
Loading…
Reference in New Issue
Block a user