From a290f445efe812ad4886ca23cca00c8bb3b48c2b Mon Sep 17 00:00:00 2001 From: Tim Burke Date: Mon, 17 Jun 2024 14:43:10 -0700 Subject: [PATCH] CI: make sure old swift is truly gone for rolling-upgrade jobs While switching how some executable scripts were configured, I saw some strange rolling-upgrade failures that seemed to indicate that the new invocation method was trying to be used with old code. It seems like it maybe has something to do with whether swift was installed to /usr/local/lib/python3.9/site-packages/ or /usr/local/lib64/python3.9/site-packages/ but I'm not entirely sure. At any rate, a proper package manager ought to uninstall the old version then install the new one, so it seems reasonable to do that with pip, too. Change-Id: I12e84745e7601d162755bc9d0f1cda7b63e92197 --- tools/playbooks/multinode_setup/run.yaml | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/tools/playbooks/multinode_setup/run.yaml b/tools/playbooks/multinode_setup/run.yaml index 5ea82fa31c..6682ee1e7b 100644 --- a/tools/playbooks/multinode_setup/run.yaml +++ b/tools/playbooks/multinode_setup/run.yaml @@ -13,6 +13,13 @@ - hosts: storage tasks: + - name: remove old swift + become: true + shell: + cmd: pip uninstall -y swift + executable: /bin/bash + chdir: '{{ zuul.project.src_dir }}' + - name: checkout master swift shell: cmd: git checkout master