[SERVER-33813] launch_evergreen_ec2_instance.sh should immediately fail if the call to aws_ec2.py is unsuccessful Created: 12/Mar/18  Updated: 29/Oct/23  Resolved: 03/Apr/18

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 3.6.6, 3.7.4

Type: Bug Priority: Major - P3
Reporter: Jonathan Abrahams Assignee: Jonathan Abrahams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6
Sprint: TIG 2018-04-09
Participants:
Linked BF Score: 0

 Description   

The status of calling aws_ec2.py to create an AWS EC2 instance needs to be checked. The launch_evergreen_ec2_instance.sh script fail immediately, if unsuccessful. Since the call to aws_ec2.py is in a subshell, the script will not exit from set -o errexit.



 Comments   
Comment by Githook User [ 30/May/18 ]

Author:

{'username': 'hptabster', 'name': 'Jonathan Abrahams', 'email': 'jonathan@mongodb.com'}

Message: SERVER-33813 launch_evergreen_ec2_instance.sh should immediately fail if the call to aws_ec2.py is unsuccessful

(cherry picked from commit 5fa649cf8e0b77020d680c554aef1d380605611b)
Branch: v3.6
https://github.com/mongodb/mongo/commit/5438e5b2998e29e2c0cd75372a746475a9c61302

Comment by Githook User [ 03/Apr/18 ]

Author:

{'email': 'jonathan@mongodb.com', 'name': 'Jonathan Abrahams', 'username': 'hptabster'}

Message: SERVER-33813 launch_evergreen_ec2_instance.sh should immediately fail if the call to aws_ec2.py is unsuccessful
Branch: master
https://github.com/mongodb/mongo/commit/5fa649cf8e0b77020d680c554aef1d380605611b

Comment by Max Hirschhorn [ 13/Mar/18 ]

I think we should consider moving the writing of the aws_ec2.yml file into Python so that we don't even need to parse the output of the aws_ec2.py script to determine the IP address of the spawned host.

Generated at Thu Feb 08 04:34:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.