Bug #2712
Net::SSH::Disconnect not handled in SSH provisioning
Description
Some premade Openstack images set up SSH keys as part of cloud-init. This means SSH comes up initially without and host keys and refuses connections for 10-15 seconds while the keys are created during the cloud-init run.
Since we don't catch Net::SSH::Disconnect Foreman sees the disconnect as an error and immediately fails the job. We should catch the error and retry (as we do for other exceptions) and lengthen the timeout to account for the cloud-init startup time.
Associated revisions
Fixes #2712 - Handle Net::SSH::Disconnect gracefully
(cherry picked from commit 0b5d270d9fcb1fae39b5d9e3b8bbd4999e710882)
History
#1
Updated by Dominic Cleal about 6 years ago
Updated by - Status changed from Assigned to Ready For Testing
#2
Updated by Greg Sutcliffe about 6 years ago
Updated by - Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset be49e1eebcf1e9b616cd404cae941c22903f1cb7.
Fixes #2712 - Handle Net::SSH::Disconnect gracefully