Actions
Bug #35924
closedssh is not able to detect if the remote host just stops responding
Difficulty:
Triaged:
No
Bugzilla link:
Description
Local libvirt reproducer:
1) Have foreman and a vm
2) Run long running ssh job against the vm
3) Do shut down > force off on the vm (or iptables -I INPUT -j DROP on the remote host could have the same effect)
Expected result:
The job breaks
Actual result:
The job hangs
Updated by Adam Ruzicka about 2 years ago
- Copied to Bug #35925: ansible is not able to detect if the remote host just stops responding added
Updated by The Foreman Bot about 2 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/smart_proxy_remote_execution_ssh/pull/100 added
Updated by The Foreman Bot about 2 years ago
- Fixed in Releases smart_proxy_remote_execution_ssh-0.10.0 added
Updated by Adam Ruzicka about 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_proxy_plugin|f273fd693b5f049cde661d7568e7d85345913496.
Updated by Adam Ruzicka about 2 years ago
- Fixed in Releases smart_proxy_remote_execution_ssh-0.10.1 added
- Fixed in Releases deleted (
smart_proxy_remote_execution_ssh-0.10.0)
Actions