Skip to main content
It didn't work
Source Link
Peter Turner
  • 1.6k
  • 4
  • 17
  • 37

The cure (or bandaid) was to set Pipelining=False in the ansible.cfg file.

This kind of stinks because I like Pipelining and it works, but I guess ansible is gonna treat that first ssh statement as something 'it owns' even though it's a local action.

Try doing the portforwarding in the module and seeing if that makes doesn't confuse ansible.

The cure (or bandaid) was to set Pipelining=False in the ansible.cfg file.

This kind of stinks because I like Pipelining and it works, but I guess ansible is gonna treat that first ssh statement as something 'it owns' even though it's a local action.

Try doing the portforwarding in the module and seeing if that makes doesn't confuse ansible.

The cure (or bandaid) was to set Pipelining=False in the ansible.cfg file.

This kind of stinks because I like Pipelining and it works, but I guess ansible is gonna treat that first ssh statement as something 'it owns' even though it's a local action.

Source Link
Peter Turner
  • 1.6k
  • 4
  • 17
  • 37

The cure (or bandaid) was to set Pipelining=False in the ansible.cfg file.

This kind of stinks because I like Pipelining and it works, but I guess ansible is gonna treat that first ssh statement as something 'it owns' even though it's a local action.

Try doing the portforwarding in the module and seeing if that makes doesn't confuse ansible.