DOC: Add how to collect from remote hosts that exceed the default host collect timeout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Elisamara Aoki Gonçalves |
Bug Description
Brief Description
-----------------
The current "Collect Caveats and Usage" documentation needs to explain how to collect from a remote host that exceeds the default host collect timeout.
Customer support organization shared with me the confusion the current documentation can lead to in this 'host collect timeout' case.
sysadmin@
[sudo] password for sysadmin:
collect bundle timeout set to 60 minutes
collecting data from 1 host(s): controller-1
collecting controller-
Support tried to use the newly introduced --timeout option with the expectation that would solve this problem. However, the --timeout specifies a global or system level collect timeout rather than a host level timeout.
That update link is below, notice the first paragraph in the description
This update adds a new --timeout command line option to the collect
tool so that users can extend collect's global timeout.
Update: Add --timeout option to collect tool
https:/
That update did not affect the 10 minute default timeout for collecting from a remote host.
There was a subsequent update that consolidated collect's default timeout settings into a file stored in the read/write /etc filesystem.
Update: Increase collect ssh, scp and sudo expect operation timeouts
https:/
/etc/collect/
# default timeouts for collect ; in seconds
declare -i SCP_TIMEOUT_
declare -i SSH_TIMEOUT_
declare -i SUDO_TIMEOUT_
declare -i COLLECT_
declare -i CREATE_
declare -i TIMEOUT_MIN_MINS=10
declare -i TIMEOUT_
declare -i TIMEOUT_DEF_MINS=20
The existing customer documentation should be updated to point out the following clarification and options
A. Enhance the description of the fact that the --timeout <mins> option extends the overall timeout of that collect operation. It does not apply to or affect the default per remote host collect timeout.
B. point out that the timeout for collecting from the local host, the host that collect is run from, does adopt the global timeout.
C. There are two ways to deal with this case
run collect with an extended --timeout locally on the host that is experiencing the timeout. That way the global timeout applies.
optionally, modify the default COLLECT_
Severity
--------
<Minor: System/Feature is usable with minor issue>
Changed in starlingx: | |
assignee: | nobody → Elisamara Aoki Gonçalves (egoncalv) |
Changed in starlingx: | |
importance: | Undecided → Low |
Fix proposed to branch: master /review. opendev. org/c/starlingx /docs/+ /921395
Review: https:/