From 1ca6223dd0d67198ecc717c67a734a3845c5f043 Mon Sep 17 00:00:00 2001 From: Alfredo Deza Date: Wed, 16 Mar 2016 11:02:33 -0400 Subject: [PATCH] clarify further why we need to call ansible to get python 2.6 Signed-off-by: Alfredo Deza --- radosgw-agent-pull-requests/build/build | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/radosgw-agent-pull-requests/build/build b/radosgw-agent-pull-requests/build/build index d7c3aea2..7ac19b72 100644 --- a/radosgw-agent-pull-requests/build/build +++ b/radosgw-agent-pull-requests/build/build @@ -6,8 +6,15 @@ install_python_packages "pkgs[@]" # run ansible to get this current host to meet our requirements, specifying -# a local connection and 'localhost' as the host where to execute. This might look -# odd because we are using ceph-deploy playbooks. But the requirements are the same +# a local connection and 'localhost' as the host where to execute. This might +# look odd because we are using ceph-deploy playbooks. But the job-specific +# requirements are the same: install different versions of Python (including +# 2.6 and 2.7) +# +# These job-specific requirements aren't met by the services in charge of +# creating slaves (mainly prado.ceph.com) because those slaves have "generic" +# requirements and usually do not care about specific needs like Python 2.6 + cd "$WORKSPACE/ceph-build/ceph-deploy-pull-requests/setup/playbooks" $VENV/ansible-playbook -i "localhost," -c local setup.yml -- 2.39.5