Bug #19269
open
Amazon::S3 takes forever to install and is only used by three tests
Added by Nathan Cutler about 7 years ago.
Updated about 7 years ago.
Description
Amazon::S3 is only used by the following three tests:
qa/suites/rgw/multifs/tasks/rgw_bucket_quota.yaml
qa/suites/rgw/multifs/tasks/rgw_multipart_upload.yaml
qa/suites/rgw/multifs/tasks/rgw_user_quota.yaml
AFAICT for just these three tests, ceph-cm-ansible is installing Amazon::S3 (and all its dependencies), from CPAN, on every single teuthology worker machine.
Opening this ticket to explore the possibility of moving the Amazon::S3 installation into the test YAML (should be feasible, since the "cpanm" command syntax is the same everywhere).
I note that libnet-amazon-s3-perl exists in Debian-land.
- Assignee set to David Galloway
I've wondered about this since it does take a while to install. It should only have to install once however. The Ansible task checks if it's already installed and only installs if its docs are missing.
I can see how this would be an issue on ephemeral VPSes and OVH nodes. Is that where you're seeing the slow-down?
Our current OVH images already have the module installed
@David: Yes, this issue is occuring in ephemeral VMs. In some cases cephlab.ansible task is actually hanging (and timing out) at "testnode: install Amazon::S3". This started happening this past week - before, it was taking a long time (probably because the "cpan Amazon::S3" command causes the test suites of Amazon::S3 and all its dependencies to be run) but completing. It's not urgent. If it's not a problem for you, feel free to close the issue or assign it to me.
I tried "cpan Amazon::S3" on a fresh VM in OVH and could not reproduce the hang. It completed successfully after I manually installed gcc and the expat-devel package which is required by one of the Perl dependencies.
Also available in: Atom
PDF