Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable-2.7] Don't raise AnsibleConnectionFailure if the ssh process has already died. (#53534) #53691

Merged
merged 1 commit into from Mar 18, 2019

Conversation

Projects
None yet
3 participants
@sivel
Copy link
Member

sivel commented Mar 12, 2019

  • Don't raise AnsibleConnectionFailure if the ssh_process has already died. Fixes #53487

  • Better support for file not found messages

  • Add changelog fragment
    (cherry picked from commit e9f9bca)

Co-authored-by: Matt Martz matt@sivel.net

[stable-2.7] Don't raise AnsibleConnectionFailure if the ssh process …
…has already died. (#53534)

* Don't raise AnsibleConnectionFailure if the ssh_process has already died. Fixes #53487

* Better support for file not found messages

* Add changelog fragment
(cherry picked from commit e9f9bca)

Co-authored-by: Matt Martz <matt@sivel.net>

@abadger abadger merged commit abf5f75 into ansible:stable-2.7 Mar 18, 2019

1 check passed

Shippable Run 113416 status is SUCCESS.
Details
@abadger

This comment has been minimized.

Copy link
Member

abadger commented Mar 18, 2019

Merged for the 2.7.10 release.

@sivel sivel removed the needs_triage label Mar 19, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.