Risk of config update to config_volume not triggering container restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Martin André |
Bug Description
docker-puppet.py assumes there can be only one config_volume per container [1]. Unfortunately this is not true and we already have examples in t-h-t [2]. This means there is a risk paunch doesn't restart a container after a config update if the hash doesn't correspond to the config_volume that was updated.
One way to solve the issue could be to calculate a hash based on the hashes of all mounted volumes and pass that as TRIPLEO_
[1] https:/
[2] https:/
Changed in tripleo: | |
milestone: | none → queens-1 |
status: | New → Triaged |
Fix proposed to branch: master /review. openstack. org/510632
Review: https:/