In the last few weeks we have experimented that we cannot keep downloading roles inside our vagrant machine.
ansible-galaxy install geerlingguy.ntp,1.3.0
gives
- the API server (galaxy.ansible.com) is not responding, please try again later.
Inside our Vagrant box running Centos 6.7, with Ansible version ansible 1.9.4 and Python 2.6.6
ansible-galaxy install geerlingguy.ntp,1.3.0
- downloading role 'ntp', owned by geerlingguy
- downloading role from https://github.com/geerlingguy/ansible-role-ntp/archive/1.3.0.tar.gz
- extracting geerlingguy.ntp to /etc/ansible/roles/geerlingguy.ntp
Things we've tried so far:
/usr/lib/python2.6/site-packages/pip/_vendor/requests/packages/urllib3/util/ssl_.py:90: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning. so I've also installed pip install pyopenssl ndg-httpsclient pyasn (https://github.com/nephila/djangocms-installer/issues/174)Nothing seems to make it work.
What version of Ansible are you running?
FWIW, it works from the latest code in the devel branch of Ansible, just running on Mac OS:
ansible-galaxy install geerlingguy.ntp,1.3.0
- downloading role 'ntp', owned by geerlingguy
- downloading role from https://github.com/geerlingguy/ansible-role-ntp/archive/1.3.0.tar.gz
- extracting geerlingguy.ntp to /Users/chouseknecht/roles/geerlingguy.ntp
- geerlingguy.ntp (1.3.0) was installed successfully
O. I see now in your comment, 1.9.4. That's likely the problem.
Well, it actually seems to work with 1.9.4.
$ ansible --version
ansible 1.9.4
configured module search path = None
$ ansible-galaxy install geerlingguy.ntp,1.3.0
- downloading role 'ntp', owned by geerlingguy
- downloading role from https://github.com/geerlingguy/ansible-role-ntp/archive/1.3.0.tar.gz
- extracting geerlingguy.ntp to /Users/chouseknecht/roles/geerlingguy.ntp
- geerlingguy.ntp was installed successfully
It feels like this is related to the SNI issue, which we鈥檙e working on.
Closing as a duplicate of #795. We have a workaround for systems running Python < 2.7.9 (see #795), and we will add it to our docs.
ok @chouseknecht, thanks !
Most helpful comment
It feels like this is related to the SNI issue, which we鈥檙e working on.