Description of problem:
When OpenSSH's client settings specify ConnectTimeout as 0 (zero), net/ssh will immediately timeout when attempting an SSH connection. In contrast, openssh-client (the ssh command) will complete successfully using the exact same client config file.
This is preventing Satellite 6.3.0 from running remote execution jobs if "ConnectTimeout 0" is set in either ~foreman-proxy/.ssh/config or /etc/ssh/ssh_config.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add this content to /etc/ssh/ssh_config on a Satellite 6.3:
2. Attempt to run any remote execution job.
Fails every time with:
Error initializing command: Net::SSH::ConnectionTimeout - Net::SSH::ConnectionTimeout
Exit status: EXCEPTION
It should interpret "ConnectTimeout 0" exactly like the openssh client utility does. Apparently openssh client will ignore ConnectTimeout if set to 0.
This issue is new to Satellite 6.3.0.
Changing the @server_version declaration in line 84 of usr/share/gems/gems/net-ssh-4.0.1/lib/net/ssh/transport/session.rb to set any integer instead of relying on options[:timeout] resolved the issue during my tests.
is there any update on this bug
Seems this bug is still exits in satellite 6.3.3, let me know thw status.
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.