From be08a064b609d24fe61fa7d187bd9c88bc4a3b3a Mon Sep 17 00:00:00 2001 From: Jean-Philippe Evrard Date: Tue, 28 Feb 2017 14:21:10 +0000 Subject: [PATCH] Use an explicit version of urrlib3 If not forcing to install urllib3, ansible on the deploy node will reuse the urrlib3 from site-packages, which could be older than the one in global-requirements, because ansible doesn't list it in its dependencies, so we don't explicit force a certain version to be installed. On my machine, I had an urllib3 installed with a version of 1.7.1, and all the lookups with https had SSL issues. Moving to urllib3 fixed the thing. This only cares about the ansible side, to ensure ansible venv has the proper version. Hosts targetted by ansible (for example when using get_url), also need a fix. This will be done in different patches. Change-Id: Ia07969ac9aee90724eecc6657affd1dbe16045a7 --- requirements.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/requirements.txt b/requirements.txt index eda5c652cf..718481433c 100644 --- a/requirements.txt +++ b/requirements.txt @@ -13,4 +13,5 @@ PrettyTable<0.8,>=0.7.1 # BSD pycrypto>=2.6 # Public Domain python-memcached>=1.56 # PSF PyYAML>=3.10.0 # MIT +urllib3>=1.15.1 # MIT virtualenv>=13.1.0 # MIT