Public bug reported:
A while ago, we changed the ec2 publishing scripts to launch instances
in each region concurrently rather than serially during the publish to
ebs phase.
Ever since then, in a build failure, there was the possibility of an instance
being orphaned and never killed.
That resulted in m1.large instances sitting around doing nothing, and charging
us money.
I'd then find them later and kill them, but damage was done.
We need do do everything we can to not leak have instances left running.
I think there are 2 things to do here:
a.) fix the scripts so that they correctly terminate instances on failure
b.) in the event of future failure, having a 'reaper' that would kill
instances up to long.
** Affects: ubuntu
Importance: Medium
Assignee: Scott Moser (smoser)
Status: In Progress
** Tags: cloud-images ec2-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/927823
Title:
publish-build-ebs can leak instances
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/927823/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
