swift/tools/playbooks
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
..
ceph-s3tests CI: Run s3api test suite 2022-05-27 23:46:20 -07:00
common CI: Move probe tests to centos 9 stream 2024-03-15 08:09:25 -07:00
cors CI: Move probe tests to centos 9 stream 2024-03-15 08:09:25 -07:00
dsvm dsvm: Run service-user tests under tempauth 2020-05-26 12:54:17 -07:00
multinode_setup CI: make sure old swift is truly gone for rolling-upgrade jobs 2024-06-17 15:01:35 -07:00
probetests Switch to pytest 2022-12-09 11:38:02 -08:00
s3api-tests CI: Run s3api test suite 2022-05-27 23:46:20 -07:00
saio_single_node_setup playbooks: replace ansible_ssh_user with ansible_user 2022-10-11 11:27:03 +01:00