From b34c442fcbb3bb1738768243512d3922d270cca1 Mon Sep 17 00:00:00 2001 From: Ian Wienand Date: Thu, 18 Oct 2018 08:18:29 +1100 Subject: [PATCH] wheel-mirror: serialise copies to AFS This is a follow-on to I3761dd9d2ab752e66bcccdd2434405f11535b95f where I misunderstood what "linear" was doing. What was really intended was to stop both the python2 and python3 builds copying to AFS at the same time. "linear" just means the *tasks* start at the same time across hosts; not that they run serially. To do that you want the (aptly named) "serial" specifier on the playbook. Add this so we do the copies sequentially Change-Id: I4f8a2f2c6c8164e7ea207f8e4b286e06df0b13dd --- playbooks/publish/wheel-mirror.yaml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/playbooks/publish/wheel-mirror.yaml b/playbooks/publish/wheel-mirror.yaml index 7531d8a4a0..50fe752655 100644 --- a/playbooks/publish/wheel-mirror.yaml +++ b/playbooks/publish/wheel-mirror.yaml @@ -1,5 +1,10 @@ - hosts: all - strategy: linear + # We don't want the python2 & python3 hosts copying to AFS at the + # same time. In some cases for generic wheels they can have + # produced a file with the same name and thus we open a window to + # corruption on AFS with multiple simultaneous writers to the same + # file. + serial: 1 pre_tasks: - name: Generate AFS slug - CentOS