1037786b6c
We currently create /var/lib/docker-puppet/docker-puppet.sh inside the mp_puppet_config() function which then gets invoked in parallel via the following: p = multiprocessing.Pool(process_count) returncodes = list(p.map(mp_puppet_config, process_map)) This is problematic because we have the following potential race: 1) Process A opens /var/lib/docker-puppet/docker-puppet.sh for writing 2) Process B runs docker run and has the following bind mount: /var/lib/docker-puppet/docker-puppet.sh:/var/lib/docker-puppet/docker-puppet.sh:z 3) Process B will fail because an exec of a file being written to will return ETXTBSY The deployment can fail due to the above with the following error: [root@overcloud-controller-2 ~]# docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES a401108cd827 192.168.24.1:8787/tripleoqueens/centos-binary-glance-api:current-tripleo-rdo "/var/lib/docker-p..." 19 minutes ago Exited (1) 19 minutes ago docker-puppet-glance_api [root@overcloud-controller-2 ~]# docker logs docker-puppet-glance_api standard_init_linux.go:178: exec user process caused "text file busy" Since /var/lib/docker-puppet/docker-puppet.sh never changes there is really no need to create it multiple times. Let's just create it once before spawning the multiple docker run commands so we avoid any ETXTBSY errors. Ran 20 successful deployments in sequence with this change applied. Change-Id: I16b19488ce9f1411273459576db76d16b318dacb Closes-Bug: #1760787 |
||
|---|---|---|
| .. | ||
| services | ||
| README-containers.md | ||
| docker-puppet.py | ||
| docker-toool | ||