Add markupsafe to pip install list

[derek-meulmeester]

I followed the install from source and was getting the following error:
ImportError: No module named markupsafe

I had to install the markupsafe package as well, so I think it makes sense to add it to the pip install list.
I ran the install on Mac OSX 10.9.2

[mpdehaan]

Somehow I got by without installing this and I think it was brought it as a library dependency. We can investigate.

[derek-meulmeester]

Interesting, for what its worth here are the various versions I have installed as well:
Python 2.7.6

paramiko (1.13.0)
PyYAML (3.11)
Jinja2 (2.7.2)
httplib2 (0.9)

And then after installing markupsafe
MarkupSafe (0.21)

[sivel]

MarkupSafe is a dependency of jinja2:

https://github.com/mitsuhiko/jinja2/blob/master/setup.py#L83

[derek-meulmeester]

I see, it's a dependency for 2.8. Which is not (currently) the latest stable release and not what pip will install. I suppose since it will be part of 2.8 then it doesn't make sense to add it to the pip install list.

Thanks

[derek-meulmeester]

actually I do see it as a dependency of 2.7.2:
https://github.com/mitsuhiko/jinja2/blob/2.7.2/setup.py

Why didn't it install it for me then ?

[mpdehaan]

Don't know, can't reproduce this so I am going to close this ticket.

Please let me know if you figure out why or encounter any additional problems.

[DragonBe]

I had the same issue as reported by @derek-meulmeester using Mac OS X 10.9.2.

I didn't had anything of Python installed prior to getting started with Ansible and I ran into the exact same issue:

After installing markupsafe, using pip install markupsafe I was able to execute ansible all -m ping --ask-pass but got again an error regarding sshpass.

After following the instructions given at http://thornelabs.net/2014/02/09/ansible-os-x-mavericks-you-must-install-the-sshpass-program.html I stumbled upon another issue.

127.0.0.1 | FAILED => SSH encountered an unknown error during the connection. We recommend you re-run the command using -vvvv, which will enable SSH debugging output to help diagnose the issue

When enabling debugging ansible all -m ping --ask-pass -vvvv I got some more information on what went wrong:

127.0.0.1 | FAILED => SSH encountered an unknown error. The output was:
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /Users/dragonbe/.ssh/config
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 102: Applying options for *
debug1: auto-mux: Trying existing master
debug1: Control socket "/Users/dragonbe/.ansible/cp/ansible-ssh-127.0.0.1-22-dragonbe" does not exist
debug2: ssh_connect: needpriv 0
debug1: Connecting to 127.0.0.1 [127.0.0.1] port 22.
debug2: fd 3 setting O_NONBLOCK
debug1: connect to address 127.0.0.1 port 22: Connection refused
ssh: connect to host 127.0.0.1 port 22: Connection refused

Apparently I needed to enable connection sharing, as described on http://www.sawantshah.com/tech-talk/resolution-of-ansible-issues-on-os-x-mavericks/ but still bumping agains errors:

127.0.0.1 | FAILED => Using a SSH password instead of a key is not possible because Host Key checking is enabled and sshpass does not support this.  Please add this host's fingerprint to your known_hosts file to manage this host.

To solve this, I quickly logged in using ssh: ssh 127.0.0.1 which allowed me to add my host's fingerprint to the ~/.ssh/known_hosts file.

The authenticity of host '127.0.0.1 (127.0.0.1)' can't be established.
RSA key fingerprint is 22:4d:56:ef:72:a6:fd:11:7e:44:7d:1b:23:da:88:42.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '127.0.0.1' (RSA) to the list of known hosts.

And finally I was able to get my result!

127.0.0.1 | success >> {
    "changed": false,
    "ping": "pong"
}

So, this information might be interesting to add to the documentation though. If you want to reproduce this, use a cleaned install mac os x with 10.9.2, update the system, enable firewall and start installation of ansible as described on http://docs.ansible.com/intro_installation.html#running-from-source