# Ansible 1.9.1 Released

**URL:** <https://forum.ansible.com/t/ansible-1-9-1-released/18113>\
**Category:** Ansible Project\
**Created:** [April 28, 2015, 6:50pm UTC](https://forum.ansible.com/t/ansible-1-9-1-released/18113 "2015-04-28T18:50:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\
**Post date:** [April 28, 2015, 6:50pm UTC](https://forum.ansible.com/t/ansible-1-9-1-released/18113/1 "2015-04-28T18:50:36Z")

</div>

Hi all, Ansible 1.9.1 final has been released and is now available.

Ansible 1.9.1 fixes several bugs, including:

- Fixed a bug related to Kerberos auth when using winrm with a domain account.
- Fixing several bugs in the s3 module.
- Fixed a bug with upstart service detection in the service module.
- Fixed several bugs with the user module when used on OSX.
- Fixed unicode handling in some module situations (assert and shell/command execution).
- Fixed a bug in redhat\_subscription when using the activationkey parameter.
- Fixed a traceback in the gce module on EL6 distros when multiple pycrypto installations are available.
- Added support for PostgreSQL 9.4 in rds\_param\_group
- Several other minor fixes.

As always, this update is available via PyPi and [releases.ansible.com](http://releases.ansible.com) now, and packages for distros will be available as soon as possible.

Thanks, and enjoy!

---

<div class="post-metadata">

**Author:** ![Arturas\_Slajus](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@Arturas\_Slajus](https://forum.ansible.com/u/Arturas_Slajus)\
**Post date:** [April 29, 2015, 7:49am UTC](https://forum.ansible.com/t/ansible-1-9-1-released/18113/2 "2015-04-29T07:49:12Z")

</div>

Just updated to 1.9.1 from ubuntu PPA, and ansible-playbook doesn’t ask for sudo pass anymore.

arturas@zeus:~/work/tlp-ansible/setup$ ansible-playbook -s nebula-client.yml

PLAY [setup servers for hosting nebula 44 client] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*

TASK: [ensuring user is present] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
failed: [[worg.nebula44.com](http://worg.nebula44.com)] =\> {“failed”: true, “parsed”: false}  
OpenSSH\_6.6.1, OpenSSL 1.0.1f 6 Jan 2014  
debug1: Reading configuration data /home/arturas/.ssh/config  
debug1: Reading configuration data /etc/ssh/ssh\_config  
debug1: /etc/ssh/ssh\_config line 19: Applying options for \*  
debug1: auto-mux: Trying existing master  
debug1: Control socket “/home/arturas/.ansible/cp/ansible-ssh-worg.nebula44.com-22-config” does not exist  
debug1: Connecting to [worg.nebula44.com](http://worg.nebula44.com) [46.166.165.65] port 22.  
debug1: fd 3 clearing O\_NONBLOCK  
debug1: Connection established.  
debug1: identity file /home/arturas/.ssh/id\_rsa type 1  
debug1: identity file /home/arturas/.ssh/id\_rsa-cert type -1  
debug1: identity file /home/arturas/.ssh/id\_dsa type -1  
debug1: identity file /home/arturas/.ssh/id\_dsa-cert type -1  
debug1: identity file /home/arturas/.ssh/id\_ecdsa type -1  
debug1: identity file /home/arturas/.ssh/id\_ecdsa-cert type -1  
debug1: identity file /home/arturas/.ssh/id\_ed25519 type -1  
debug1: identity file /home/arturas/.ssh/id\_ed25519-cert type -1  
debug1: Enabling compatibility mode for protocol 2.0  
debug1: Local version string SSH-2.0-OpenSSH\_6.6.1p1 Ubuntu-2ubuntu2  
debug1: Remote protocol version 2.0, remote software version OpenSSH\_6.6.1p1 Ubuntu-2ubuntu2  
debug1: match: OpenSSH\_6.6.1p1 Ubuntu-2ubuntu2 pat OpenSSH\_6.6.1\* compat 0x04000000  
debug1: SSH2\_MSG\_KEXINIT sent  
debug1: SSH2\_MSG\_KEXINIT received  
debug1: kex: server-\>client aes128-ctr [hmac-md5-etm@openssh.com](mailto:hmac-md5-etm@openssh.com) [zlib@openssh.com](mailto:zlib@openssh.com)  
debug1: kex: client-\>server aes128-ctr [hmac-md5-etm@openssh.com](mailto:hmac-md5-etm@openssh.com) [zlib@openssh.com](mailto:zlib@openssh.com)  
debug1: sending SSH2\_MSG\_KEX\_ECDH\_INIT  
debug1: expecting SSH2\_MSG\_KEX\_ECDH\_REPLY  
debug1: Server host key: ECDSA eb:28:8c:94:6c:14:c6:96:a3:b9:e2:87:fb:be:51:19  
debug1: Host ‘[worg.nebula44.com](http://worg.nebula44.com)’ is known and matches the ECDSA host key.  
debug1: Found key in /home/arturas/.ssh/known\_hosts:219  
debug1: ssh\_ecdsa\_verify: signature correct  
debug1: SSH2\_MSG\_NEWKEYS sent  
debug1: expecting SSH2\_MSG\_NEWKEYS  
debug1: SSH2\_MSG\_NEWKEYS received  
debug1: Roaming not allowed by server  
debug1: SSH2\_MSG\_SERVICE\_REQUEST sent  
debug1: SSH2\_MSG\_SERVICE\_ACCEPT received  
debug1: Authentications that can continue: publickey  
debug1: Next authentication method: publickey  
debug1: Offering RSA public key: /home/arturas/.ssh/id\_rsa  
debug1: Server accepts key: pkalg ssh-rsa blen 277  
debug1: Enabling compression at level 6.  
debug1: Authentication succeeded (publickey).  
Authenticated to [worg.nebula44.com](http://worg.nebula44.com) ([46.166.165.65]:22).  
debug1: setting up multiplex master socket  
debug1: channel 0: new [/home/arturas/.ansible/cp/ansible-ssh-worg.nebula44.com-22-config]  
debug1: control\_persist\_detach: backgrounding master process  
debug1: forking to background  
debug1: Entering interactive session.  
debug1: multiplexing control connection  
debug1: channel 1: new [mux-control]  
debug1: channel 2: new [client-session]  
debug1: Sending environment.  
debug1: Sending env LC\_PAPER = lt\_LT.UTF-8  
debug1: Sending env LC\_ADDRESS = lt\_LT.UTF-8  
debug1: Sending env LC\_MONETARY = lt\_LT.UTF-8  
debug1: Sending env LC\_NUMERIC = lt\_LT.UTF-8  
debug1: Sending env LC\_TELEPHONE = lt\_LT.UTF-8  
debug1: Sending env LC\_IDENTIFICATION = lt\_LT.UTF-8  
debug1: Sending env LANG = en\_US.UTF-8  
debug1: Sending env LC\_MEASUREMENT = lt\_LT.UTF-8  
debug1: Sending env LC\_TIME = lt\_LT.UTF-8  
debug1: Sending env LC\_NAME = lt\_LT.UTF-8  
debug1: Sending command: /bin/sh -c ‘sudo -k && sudo -H -S -p “[sudo via ansible, key=esmqhybsehqvxefvwktjjclyihqpnwws] password: " -u root /bin/sh -c '”’“‘echo BECOME-SUCCESS-esmqhybsehqvxefvwktjjclyihqpnwws; LANG=en\_US.UTF-8 LC\_CTYPE=en\_US.UTF-8 /usr/bin/python’”‘"’’  
debug1: mux\_client\_request\_session: master session id: 2  
[sudo via ansible, key=esmqhybsehqvxefvwktjjclyihqpnwws] password: Sorry, try again.  
[sudo via ansible, key=esmqhybsehqvxefvwktjjclyihqpnwws] password: Sorry, try again.  
[sudo via ansible, key=esmqhybsehqvxefvwktjjclyihqpnwws] password: Sorry, try again.  
sudo: 3 incorrect password attempts  
debug1: client\_input\_channel\_req: channel 2 rtype exit-status reply 0  
debug1: client\_input\_channel\_req: channel 2 rtype [eow@openssh.com](mailto:eow@openssh.com) reply 0  
debug1: channel 2: free: client-session, nchannels 3  
debug1: channel 1: free: mux-control, nchannels 2

FATAL: all hosts have already failed – aborting

Even though:

arturas@zeus:~/work/tlp-ansible/setup$ cat ansible.cfg  
[defaults]  
hostfile = hosts  
remote\_user = config  
ask\_sudo\_pass = yes

[ssh\_connection]  
pipelining=True

Worked perfectly on 1.9.0.
