diff options
| author | Julia Kreger <juliaashleykreger@gmail.com> | 2020-07-22 10:35:38 -0700 |
|---|---|---|
| committer | Julia Kreger <juliaashleykreger@gmail.com> | 2020-07-22 10:41:07 -0700 |
| commit | 67e51af6d55b9a7aa91adfd132ad575373229468 (patch) | |
| tree | fcefc78be25d034baf72d8f6cd934d5b88216529 /devstack/lib | |
| parent | b5ae75a4068e3f4bc1d3ab0c515b1180a909a255 (diff) | |
| download | ironic-67e51af6d55b9a7aa91adfd132ad575373229468.tar.gz | |
Extend PXE boot retry timeout for RAX hosts
When extending the timeouts for jobs to execute with-in,
we've observed a case where RAX hosts are cutting off at
the time limit of 900 seconds (as being asserted by another
change set). This is both good and bad. We know the timeout
feature works, but the agent was not quite online yet.
As such, we should also auto-extend base retry timeouts
so there is hope for the job to complete.
Change-Id: I8efa3a52188de558a7964d1daafd2225e102e251
Diffstat (limited to 'devstack/lib')
| -rw-r--r-- | devstack/lib/ironic | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/devstack/lib/ironic b/devstack/lib/ironic index 7b0482dd7..40cbd6b26 100644 --- a/devstack/lib/ironic +++ b/devstack/lib/ironic @@ -173,6 +173,13 @@ if [[ "$hostdomain" =~ "rax" ]]; then # these hosts for jobs to complete without issues. new_timeout=$(echo "$IRONIC_TEMPEST_BUILD_TIMEOUT * 1.5 / 1" | bc) IRONIC_TEMPEST_BUILD_TIMEOUT=$new_timeout + + if [ -n "$IRONIC_PXE_BOOT_RETRY_TIMEOUT" ]; then + new_timeout=$(echo "$IRONIC_PXE_BOOT_RETRY_TIMEOUT * 1.5 / 1" | bc) + IRONIC_PXE_BOOT_RETRY_TIMEOUT=$new_timeout + fi + # TODO(TheJulia): If we have to do magically extend timeouts again, + # we should make a helper method... fi IRONIC_DEFAULT_API_VERSION=${IRONIC_DEFAULT_API_VERSION:-} |