From ec76eeb2f53e97ff66961924a47809f9ca800ac8 Mon Sep 17 00:00:00 2001 From: Fabio Gelcer Date: Thu, 9 Nov 2023 16:37:36 +0200 Subject: [PATCH] fix(longevity-alternator-3h): set different default AZ since this test is running on `i4i.4xlarge` by default, and the availability for these instances on AZ `a` is minimal, as the following error shows: ``` (InsufficientInstanceCapacity) when calling the RunInstances operation (reached max retries: 4): We currently do not have sufficient i4i.4xlarge capacity in the Availability Zone you requested (us-east-1a). Our system will be working on provisioning additional capacity. You can currently get i4i.4xlarge capacity by not specifying an Availability Zone in your request or choosing us-east-1b, us-east-1c, us-east-1d, us-east-1f. ``` moving the default to `c` did make the 5.4 job at least start, so sending this PR to change the default, to increase the chance of success. --- jenkins-pipelines/longevity-alternator-3h.jenkinsfile | 1 + 1 file changed, 1 insertion(+) diff --git a/jenkins-pipelines/longevity-alternator-3h.jenkinsfile b/jenkins-pipelines/longevity-alternator-3h.jenkinsfile index a27f4206c7..49b0cf7b5c 100644 --- a/jenkins-pipelines/longevity-alternator-3h.jenkinsfile +++ b/jenkins-pipelines/longevity-alternator-3h.jenkinsfile @@ -6,6 +6,7 @@ def lib = library identifier: 'sct@snapshot', retriever: legacySCM(scm) longevityPipeline( backend: 'aws', region: 'eu-west-1', + availability_zone: 'c', test_name: 'longevity_test.LongevityTest.test_custom_time', test_config: 'test-cases/longevity/longevity-alternator-3h.yaml',