swift/tools/playbooks/multinode_setup
Tim Burke a290f445ef 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
2024-06-17 15:01:35 -07:00
..
templates playbooks: replace ansible_ssh_user with ansible_user 2022-10-11 11:27:03 +01:00
common_config.yaml playbooks: replace ansible_ssh_user with ansible_user 2022-10-11 11:27:03 +01:00
configure_loopback.yaml docs: Clean up mount options 2020-05-03 00:43:57 -07:00
make_rings.yaml playbooks: replace ansible_ssh_user with ansible_user 2022-10-11 11:27:03 +01:00
pre.yaml CI: Run ceph and rolling upgrade tests under py3 2022-04-04 17:17:06 -07:00
run.yaml CI: make sure old swift is truly gone for rolling-upgrade jobs 2024-06-17 15:01:35 -07:00