unsupported connection type: ssh

217 views
Skip to first unread message

Trevor G

unread,
Dec 9, 2014, 1:55:55 PM12/9/14
to ansible...@googlegroups.com
I hadn't used Ansible on my laptop for a while, and now when returning to projects that I was working on before, I'm stuck on a fatal:

   fatal: [test-centos01] => unsupported connection type: ssh

I'm encountering this from a project with a VagrantFile that used to boot and provision just fine.  I can't seem to find anything describing why that may fail and how I could possibly correct it.  I'm using:

* MacOS 10.10.1
* ansible 1.7.1
* vagrant 1.6.5
* virtual box 4.3.18

Thanks,
  Trevor

Toshio Kuratomi

unread,
Dec 9, 2014, 4:47:47 PM12/9/14
to ansible...@googlegroups.com
What command are you invoking?

I'm assuming something simple like

ansible test-centos01 -m ping

is failing with that message?

What happens if you try other connection types like:

ansible test-centos01 -c paramiko -m ping

and

ansible localhost -c local -m ping

-Toshio

Trevor G

unread,
Dec 9, 2014, 5:54:09 PM12/9/14
to ansible...@googlegroups.com
Yeah.  Here's the result of all those:

trevor:~ $ ansible apps01 -m ping -i inventory.conf
apps01 | FAILED => unsupported connection type: ssh
trevor:~ $ ansible apps01 -c paramiko -m ping -i inventory.conf
apps01 | FAILED => unsupported connection type: paramiko
trevor:~ $ ansible localhost -c local -m ping -i inventory.conf
localhost | FAILED => unsupported connection type: local
trevor:~ $ more inventory.conf
[apps]
apps01


I tried uninstalling and reinstalling ansible as well.

trevor:~ $ brew install ansible
==> Downloading http://releases.ansible.com/ansible/ansible-1.7.1.tar.gz
Already downloaded: /Library/Caches/Homebrew/ansible-1.7.1.tar.gz
==> Downloading https://pypi.python.org/packages/source/p/pycrypto/pycrypto-2.6.tar.gz
Already downloaded: /Library/Caches/Homebrew/ansible--pycrypto-2.6.tar.gz
==> python setup.py install --prefix=/usr/local/Cellar/ansible/1.7.1/libexec
==> Downloading https://pypi.python.org/packages/source/P/PyYAML/PyYAML-3.10.tar.gz
Already downloaded: /Library/Caches/Homebrew/ansible--pyyaml-3.10.tar.gz
==> python setup.py install --prefix=/usr/local/Cellar/ansible/1.7.1/libexec
==> Downloading https://pypi.python.org/packages/source/p/paramiko/paramiko-1.11.0.tar.gz
Already downloaded: /Library/Caches/Homebrew/ansible--paramiko-1.11.0.tar.gz
==> python setup.py install --prefix=/usr/local/Cellar/ansible/1.7.1/libexec
==> Downloading https://pypi.python.org/packages/source/M/MarkupSafe/MarkupSafe-0.18.tar.gz
Already downloaded: /Library/Caches/Homebrew/ansible--markupsafe-0.18.tar.gz
==> python setup.py install --prefix=/usr/local/Cellar/ansible/1.7.1/libexec
==> Downloading https://pypi.python.org/packages/source/J/Jinja2/Jinja2-2.7.1.tar.gz
Already downloaded: /Library/Caches/Homebrew/ansible--jinja2-2.7.1.tar.gz
==> python setup.py install --prefix=/usr/local/Cellar/ansible/1.7.1/libexec
==> python setup.py install --prefix=/usr/local/Cellar/ansible/1.7.1
🍺  /usr/local/Cellar/ansible/1.7.1: 495 files, 6.1M, built in 10 seconds

trevor:~ $ ansible localhost -c local -m ping -i inventory.conf
localhost | FAILED => unsupported connection type: local

I'm not sure if this could be a Yosemite issue.

---------

Ok, I did another clean install, this time via `sudo pip install ansible`.  The pip installation pulled down version 1.8.2.  It looks like that is now working with my laptop.  I'm guessing it was in issue with 1.7.1.


trevor:~ $ ansible --version
ansible 1.8.2
  configured module search path = None
trevor:~ $ ansible localhost -c local -m ping -i inventory.conf
localhost | success >> {
    "changed": false,
    "ping": "pong"
}


Thanks!
  Trevor

Brian Coca

unread,
Dec 9, 2014, 6:57:42 PM12/9/14
to ansible...@googlegroups.com
looks more like a broken install, it could not find any connection plugin.


--
Brian Coca
Reply all
Reply to author
Forward
0 new messages