I have a quota of 10 smalll instances, but:
$ euca-describe-instances
RESERVATION r-bzskhau8 abentley_project default
INSTANCE i-00000469 ami-00000086 10.55.60.30 10.55.60.30 running abentley 0 m1.small 2011-09-23T15:42:33Z nova aki-00000052 ari-00000053
RESERVATION r-pp0y6bc8 abentley_project default
INSTANCE i-00000479 ami-00000086 terminated abentley 7 m1.small 2011-09-23T17:30:55Z nova aki-00000052 ari-00000053
abentley@speedy:~/hacking/test-farm$ ./init-worker -n 9 --master 10.55.60.30
InstanceLimitExceeded: InstanceLimitExceeded: Instance quota exceeded. You can only run 8 more instances of this type.
Traceback (most recent call last):
File "./init-worker", line 58, in <module>
run_instances(default_image, options.instance_count, options.master)
File "./init-worker", line 45, in run_instances
check_call(call_params)
File "/usr/lib/python2.7/subprocess.py", line 511, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['euca-run-instances', '--key', 'abentley', '--instance-count', '9', 'ami-00000086', '--user-data-file', '/tmp/tmpOnphAf.sh']' returned non-zero exit status 1
^^ This is just an automated way of saying
euca-run-instances --key abentley --instance-count 9 ami-00000086 --user-data-file /tmp/tmpOnphAf.sh
Generally terminated instances are cleared away - and hence don't take up quota - so the question I'd have is why this one is hanging around. Is there a known reason for your terminated instance still being there ?