Travis failure in master: EC2 instance failed to create
See original GitHub issueNot clear if this was one-off or likely to re-occur.
https://travis-ci.com/pulumi/pulumi-cloud/builds/58711465
It looks like one of the two VMs that was created never responded that it was ready (presumably never fired the cfn-signal in it’s userdata script?).
The VM that never responded doesn’t show anything too unusual happening - it was running for the full 15 minute period:
https://us-east-2.console.aws.amazon.com/ec2/v2/home?region=us-east-2#Instances:sort=instanceState
Unfortunately we don’t have logging for the EC2 VM boot process so it’s hard to see what might have gone wrong on the VM.
Issue Analytics
- State:
- Created 6 years ago
- Comments:45 (45 by maintainers)
Top Results From Across the Web
Common Build Problems - Travis CI Docs
One possible cause for builds failing unexpectedly can be calling set -e (also known as set errexit ), either directly in your .travis.yml...
Read more >Failure in build using Travis, AWS Elasticbeanstalk and Docker
A couple things you could try: Your script command needs to set the environment var CI=true. So script: - docker run heet1996/my-profile npm ......
Read more >Troubleshoot instances with failed status checks
The following information can help you troubleshoot issues if your instance fails a status check. First determine whether your applications are exhibiting ...
Read more >Travis failures and other CI solutions - cockpit-devel - Fedora ...
We've run into an issue with travis where adding new make files causes the tests to fail with an "write error" when running...
Read more >Deal with certain travis CI failures - makandra cards
Your travis-ci builds might have started failing on the usual psql -c 'create database active_type_test;' -U postgres. with an error
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Here’s one way we can get logs from these instances, if we catch this within an hour of the failure:
Go to the list of EC2 instances in the
pulumi-testingaccount inus-east-2(Ohio). Look for terminated instances. https://us-east-2.console.aws.amazon.com/ec2/v2/home?region=us-east-2#Instances:instanceState=terminated;sort=instanceIdRight-click each terminated instance and select “Get System Log” under “Instance Settings”.
The CloudFormation event log will show us the instance that successfully came up, e.g.:
so we can look at the other one.
If there are a lot of instances, we can filter them to the appropriate autoscaling group. Looking at the CloudFormation stack will give you the physical ID of the autoscaling group. From there you can filter the EC2 instances that have a matching
aws:autoscaling:groupNametag.I tore down the termination-watcher, but here’s the code for posterity: