Limit concurrency in container-puppet to image pull
Due to a race in podman 1.6.3, when containers are created in
parallel under high disk IO, their associated overlayFS mount point
might become invalid, and container-puppet would fail to run.
In order to avoid the bug, run all docker-puppet containers
sequentially to avoid concurrent container creation. Will still
pull the images concurrently, so the time loss due to lack of
parallelism is only limited to puppet runs.
Reviewed: https:/ /review. opendev. org/699737 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=acd176e811d 39aad1d5cbc64ab 41e46dd825daf9
Committed: https:/
Submitter: Zuul
Branch: master
commit acd176e811d39aa d1d5cbc64ab41e4 6dd825daf9
Author: Damien Ciabrini <email address hidden>
Date: Wed Dec 18 18:29:19 2019 +0100
Limit concurrency in container-puppet to image pull
Due to a race in podman 1.6.3, when containers are created in
parallel under high disk IO, their associated overlayFS mount point
might become invalid, and container-puppet would fail to run.
In order to avoid the bug, run all docker-puppet containers
sequentially to avoid concurrent container creation. Will still
pull the images concurrently, so the time loss due to lack of
parallelism is only limited to puppet runs.
Change-Id: I29a9ffc621bcbd 5e1b09490c5fe09 a363286bb8b
Closes-Bug: #1856324