After installation, euca-run-instances fail unless you run euca-describe-groups first

Bug #429749 reported by Etienne Goyer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

On karmic running Eucalyptus 1.6~bzr672-0ubuntu3, after installing a node controller and registeringit successfully, it is impossible to run an instance. On the frontend:

euca-describe-availability-zones verbose
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@uec-frontend:~$ euca-describe-images
IMAGE emi-073A1120 jaunty/ubuntu.9-04.x86-64.img.manifest.xml admin available public x86_64 machine
IMAGE eri-50131678 jaunty-ramdisk/initrd.img-2.6.28-11-generic.manifest.xml admin available public x86_64 ramdisk
IMAGE eki-F2801528 jaunty-kernel/vmlinuz-2.6.28-11-generic.manifest.xml admin available public x86_64 kernel
cloudmaster@uec-frontend:~$ euca-describe-keypairs
KEYPAIR warthogs-key da:c1:0e:92:07:5c:3c:d2:51:56:10:15:7b:cf:f7:c2:f3:2c:a1:da
cloudmaster@uec-frontend:~$ euca-run-instances -t c1.medium -k warthogs-key emi-073A1120
RESERVATION None None
cloudmaster@uec-frontend:~$ euca-describe-instances
cloudmaster@uec-frontend:~$

On another machine using ec2-api-tools:

etienne@curst:~/AMI/euca-ubuntu-9.04-x86_64$ ec2-run-instances -t c1.medium -k warthogs-key emi-073A1120
GroupsVerify: Error locating information for <com.eucalyptus.entities.NetworkRulesGroup@e5d14fd3 uniqueName=admindefault description=null networkRules=[] userName=admin displayName=default id=null version=0 lastUpdate=null>
etienne@curst:~/AMI/euca-ubuntu-9.04-x86_64$ ec2-describe-instances
etienne@curst:~/AMI/euca-ubuntu-9.04-x86_64$

If I describe the security group, I am then able to launch an instance:

cloudmaster@uec-frontend:~$ euca-describe-groups
GROUP admin default default group
cloudmaster@uec-frontend:~$ euca-run-instances -t c1.medium -k warthogs-key emi-073A1120
RESERVATION r-5254095A admin admin-default
INSTANCE i-430707D2 emi-073A1120 0.0.0.0 0.0.0.0 pending warthogs-key 2009-09-14T23:52:45.132Z eki-F2801528 eri-50131678
cloudmaster@uec-frontend:~$ euca-describe-instances
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-14T23:52:45.132Z warthogs eki-F2801528 eri-50131678
cloudmaster@uec-frontend:~$

Somehow, it appears that the group information do not get initialized properly or something.

Tags: eucalyptus
Thierry Carrez (ttx)
tags: added: eucalyptus
Revision history for this message
Thierry Carrez (ttx) wrote :

Couldn't reproduce that on latest install and euca2ools. Marking as FixReleased, please reopen if you can reproduce...

Changed in eucalyptus (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.