Increase callback timeout
One of the false positives I've observed in the last 24 hours is a job where the ramdisk did not DHCP on it's network interfaces until the 550 second of runtime mark. With a callback wait of 600 seconds, this means that the deployment test job was failed moments later before the ramdisk was fully online. As such, lets move the timeout out a little as we're using larger ramdisks now, and we need to allow for a longer window at this point. Change-Id: I26bd8f2f56732be1a75518950385caeb7b439b91
This commit is contained in:
parent
c717f0e494
commit
5f24029c40
|
@ -37,7 +37,7 @@
|
|||
BUILD_TIMEOUT: 900
|
||||
IRONIC_BAREMETAL_BASIC_OPS: True
|
||||
IRONIC_BUILD_DEPLOY_RAMDISK: False
|
||||
IRONIC_CALLBACK_TIMEOUT: 600
|
||||
IRONIC_CALLBACK_TIMEOUT: 700
|
||||
IRONIC_DEPLOY_DRIVER: ipmi
|
||||
IRONIC_INSPECTOR_BUILD_RAMDISK: False
|
||||
IRONIC_TEMPEST_BUILD_TIMEOUT: 900
|
||||
|
|
Loading…
Reference in New Issue