From 0587df6e4a93c3f812f6da7aca0c3179eb0b195f Mon Sep 17 00:00:00 2001 From: Julia Kreger Date: Tue, 14 Apr 2020 12:21:41 -0700 Subject: [PATCH] Extend timeout on CI job with automated cleaning The ironic-tempest-ipa-partition-pxe_ipmitool CI job has automated cleaning enable which introduces another boot cycle where IPA starts and performs an operation. Due to the way tempest is designed with the timeouts, it appears that we are encountering one of the timeouts sporatically enough to cause a high gate failure rate. Extends the general timeout for the aformentioned test as the ramdisk takes 400+ seconds to now boot. Change-Id: I35fcf0d1f9340b0e906ea993c1b745850a4e3208 --- zuul.d/ironic-jobs.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/zuul.d/ironic-jobs.yaml b/zuul.d/ironic-jobs.yaml index 8b721d6ea5..6e41c7d984 100644 --- a/zuul.d/ironic-jobs.yaml +++ b/zuul.d/ironic-jobs.yaml @@ -254,6 +254,14 @@ description: ironic-tempest-ipa-partition-pxe_ipmitool parent: ironic-base timeout: 5400 + vars: + devstack_localrc: + # This test runs cleaning by default, and with a larger + # IPA image means that it takes longer to boot for deploy + # and cleaning. As such, CI performance variations can + # cause this job to fail easily due to the extra steps + # and boot cycle of the cleaning operation. + IRONIC_TEMPEST_BUILD_TIMEOUT: 850 - job: name: ironic-tempest-bfv