ansible 2.3.2.0 => 2.4.0.0 connection problems?

Erik Purins

unread,

Sep 19, 2017, 2:26:36 PM9/19/17

to Ansible Project

Hi everyone,

Today I made a new ansible virtualenv with 2.4.0.0 and dependencies.

A task that worked before on 2.3.2.0 is stopping with a new error.

After the task completes ok, the run stops with error:

"""

sending stop: ['ssh', '-vvv', '-C', '-o', 'ControlMaster=auto', '-o', 'ControlPersist=60s', '-o', 'KbdInteractiveAuthentication=no', '-o', 'PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey', '-o', 'PasswordAuthentication=no', '-o', 'ConnectTimeout=60', '-o', 'ControlPath=/Users/LOCALUSER/.ansible/cp/276d6f8b70', '-O', 'stop', 'None']

ERROR! Cannot reset connection:

OpenSSH_7.3p1, OpenSSL 1.0.2k 26 Jan 2017

debug1: Reading configuration data /Users/LOCALUSER/.ssh/config

debug1: /Users/LOCALUSER/.ssh/config line 68: Applying options for *

debug1: Reading configuration data /opt/local/etc/ssh/ssh_config

debug1: auto-mux: Trying existing master

Control socket connect(/Users/LOCALUSER/.ansible/cp/276d6f8b70): No such file or directory

"""

I verified the file doesn't exist, and the ControlPath parameter for all the tasks that did run previously are using a totally different ControlPath that exists.

Going back to virtualenv with ansible 2.3.2.0 and dependencies works ok.

Is this something others have seen before?

What's a good way to start debugging / troubleshooting?

-e

Matt Martz

unread,

Sep 19, 2017, 2:48:41 PM9/19/17

to ansible...@googlegroups.com

It looks like there may be a bug in the `reset_connection` meta task for the ssh connection plugin.

By the time `reset` is called, it looks like `self.host` is `None`, and as such, ssh is building an incorrect ControlPath.

Please open an issue for this.

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/8b4114d5-a492-4cbe-916f-4dd00daa610a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Matt Martz
@sivel
sivel.net

Erik Purins

unread,

Sep 19, 2017, 3:49:59 PM9/19/17

to Ansible Project

Ok Matt,

Thanks for your advice. I'll get something posted shortly.

-e

On Tuesday, September 19, 2017 at 11:48:41 AM UTC-7, Matt Martz wrote:

It looks like there may be a bug in the `reset_connection` meta task for the ssh connection plugin.

By the time `reset` is called, it looks like `self.host` is `None`, and as such, ssh is building an incorrect ControlPath.

Please open an issue for this.

On Tue, Sep 19, 2017 at 1:26 PM, Erik Purins <er...@purins.com> wrote:

Hi everyone,

Today I made a new ansible virtualenv with 2.4.0.0 and dependencies.
A task that worked before on 2.3.2.0 is stopping with a new error.

After the task completes ok, the run stops with error:
"""
sending stop: ['ssh', '-vvv', '-C', '-o', 'ControlMaster=auto', '-o', 'ControlPersist=60s', '-o', 'KbdInteractiveAuthentication=no', '-o', 'PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey', '-o', 'PasswordAuthentication=no', '-o', 'ConnectTimeout=60', '-o', 'ControlPath=/Users/LOCALUSER/.ansible/cp/276d6f8b70', '-O', 'stop', 'None']
ERROR! Cannot reset connection:
OpenSSH_7.3p1, OpenSSL 1.0.2k 26 Jan 2017
debug1: Reading configuration data /Users/LOCALUSER/.ssh/config
debug1: /Users/LOCALUSER/.ssh/config line 68: Applying options for *
debug1: Reading configuration data /opt/local/etc/ssh/ssh_config
debug1: auto-mux: Trying existing master
Control socket connect(/Users/LOCALUSER/.ansible/cp/276d6f8b70): No such file or directory
"""

I verified the file doesn't exist, and the ControlPath parameter for all the tasks that did run previously are using a totally different ControlPath that exists.
Going back to virtualenv with ansible 2.3.2.0 and dependencies works ok.

Is this something others have seen before?
What's a good way to start debugging / troubleshooting?

-e

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/8b4114d5-a492-4cbe-916f-4dd00daa610a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Brian Coca

unread,

Sep 19, 2017, 6:06:15 PM9/19/17

to Ansible Project

Tracking bug here https://github.com/ansible/ansible/issues/27520

--
----------
Brian Coca

Reply all

Reply to author

Forward