Red Hat Bugzilla – Bug 854535
PRD32 - bootstrap: support longer bootstrap duration
Last modified: 2016-02-10 14:24:56 EST
Current implementation of bootstrap installation has hard limit of 10 minutes.
This is not enough if slow connection to the internet is available.
The underline ssh library supports two types of timeouts:
Hard timeout - timeout of the entire operation.
Soft timeout - timeout since last network activity.
Having these two types of timeout enables us to extend the time of the entire process while still detecting failure of progress.
Author: Alon Bar-Lev <email@example.com>
Date: Tue Sep 4 14:05:27 2012 +0300
bootstrap: introduce soft timeouts for operations
The only place non default ssh timeout was enforced is when getting node
So it relatively simple to add soft timeout / hard timeout support by
just modify the defaults.
Hard timeout - maximum duration of command.
Soft timeout - maximum duration since last network activity.
Reduce the default of SSHInactivityTimoutSeconds to 5 minutes, it is now
the soft timeout limit.
Add a new configuration parameter of SSHInactivityHardTimoutSeconds
which is 30 minutes.
Signed-off-by: Alon Bar-Lev <firstname.lastname@example.org>
Example of user report
1. use vanilla host.
2. make sure your host is connected to the yum mirror using slow network connection.
3. perform host-deploy.
You should notice:
1. "Downloading xxx" messages at least every minute at even log.
2. defaults: SSHInactivityHardTimoutSeconds=1800, SSHInactivityTimoutSeconds=300, that's mean that unless there is 5 minutes of quiet no disconnect, and maximum duration is 30 minutes.
3. As long as the whole operation does not take more than 30 minutes it should succeed.
In the previous implementation the whole operation should have completed in something like 10 minutes, and it was hung for 10 minutes even if there was no activity.
This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
No doc is required.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.