Open osrf-migration opened 7 years ago
Original comment by Louise Poubel (Bitbucket: chapulina, GitHub: chapulina).
The reason for this is what's described on this other issue. The browser is responsible for keeping all servers in sync, and that is prone to failure.
Original report (archived issue) by Tully Foote (Bitbucket: Tully Foote, GitHub: tfoote).
If you click launch and then close the tab or reload shortly thereafter, the EC2 instance will be created, but not bookkeeped. You can later launch a new one and the original will persist in EC2.
I was able to launch both an arbiter machine as well as both blue and gold payloads using this.
Here you can see the instance with one of each payload.
But there are duplicate entries for all 3 in ec2.
And when I finish the round, the duplicates don't clean up.
They need to be manually cleaned up from the AWS console.
I've seen some instances where I believe that one of our remote users is behind a firewall and was unable to "launch" an instance. But I found a lot of instances in the AWS console which might be releated.