a5ffef4a40
A container gets a config hash if one of its bind mount references /var/lib/config-data/(puppet-generated)?/service. That hash is created/managed by container-puppet.py and stored in /var/lib/config-data/(puppet-generated)?/service.md5sum Currently, the parsing of bind-mount is broken so container-puppet.py never associates or regenerates config hashes for containers. Fix the parsing to make sure that any bind-mounts starting with /var/lib/config-data always resolve to the right md5sum file. Change-Id: I7ad50d62e6177f109f513c4c11f611be60e570f2 Closes-Bug: #1860364 |
||
---|---|---|
.. | ||
services | ||
container-puppet.py | ||
container-puppet.sh | ||
container_startup_configs_tasks.yaml | ||
deploy-steps-tasks-step-0.j2.yaml | ||
deploy-steps-tasks-step-1.yaml | ||
deploy-steps-tasks.yaml | ||
deploy-steps.j2 | ||
post.j2.yaml |