I am not sure either. But we do have some options: 1. if rejecting all requests, it should print out a reason, and end immediately; 2. if accepting up to (VNET_ADDRSPERNET - 3), then it should print out messages for the refusals (and not even try to start them) (but I guess there is a timing issue here). This is what happens when you are already at the limit, and you try another euca-run-instance on the same group.
But to accept all requests and keep them all Pending for many minutes before marking all Terminated is plainly wrong. Note that this happens from an idle system, so (on the default) we *do* have 29 instances to run. -- No instances started if euca-run-instance is run with a large -n https://bugs.launchpad.net/bugs/546293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs