After installation, euca-run-instances fail unless you run euca-describe-groups first
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
On karmic running Eucalyptus 1.6~bzr672-
euca-describe-
AVAILABILITYZONE warthogs 10.153.108.210
AVAILABILITYZONE |- vm types free / max cpu ram disk
AVAILABILITYZONE |- m1.small 0004 / 0004 1 128 2
AVAILABILITYZONE |- c1.medium 0004 / 0004 1 256 5
AVAILABILITYZONE |- m1.large 0002 / 0002 2 512 10
AVAILABILITYZONE |- m1.xlarge 0002 / 0002 2 1024 20
AVAILABILITYZONE |- c1.xlarge 0001 / 0001 4 2048 20
cloudmaster@
IMAGE emi-073A1120 jaunty/
IMAGE eri-50131678 jaunty-
IMAGE eki-F2801528 jaunty-
cloudmaster@
KEYPAIR warthogs-key da:c1:0e:
cloudmaster@
RESERVATION None None
cloudmaster@
cloudmaster@
On another machine using ec2-api-tools:
etienne@
GroupsVerify: Error locating information for <com.eucalyptus
etienne@
etienne@
If I describe the security group, I am then able to launch an instance:
cloudmaster@
GROUP admin default default group
cloudmaster@
RESERVATION r-5254095A admin admin-default
INSTANCE i-430707D2 emi-073A1120 0.0.0.0 0.0.0.0 pending warthogs-key 2009-09-
cloudmaster@
RESERVATION r-5254095A admin default
INSTANCE i-430707D2 emi-073A1120 0.0.0.0 0.0.0.0 pending warthogs-key 0 c1.medium 2009-09-
cloudmaster@
Somehow, it appears that the group information do not get initialized properly or something.
tags: | added: eucalyptus |
Couldn't reproduce that on latest install and euca2ools. Marking as FixReleased, please reopen if you can reproduce...