SCHEDPOLICY="GREEDY" does not seem to work

Bug #542075 reported by C de-Avillez
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)

Bug Description

I was following the test scenario at, specifically the "Test Case: Greedy scheduling policy".

Followed the instructions, expecting to find one NC running two images. Instead I got this:

euca-describe-instances Fri Mar 19 14:09:21 2010

RESERVATION r-384206A3 admin default
INSTANCE i-3D080709 emi-7751170A running mykey 1 c1.medium 2010-0
3-19T18:02:39.124Z UEC-TEST1 eki-D5191C21 eri-B1201B93
INSTANCE i-3E590796 emi-7751170A running mykey 0 c1.medium 2010-0
3-19T18:02:39.122Z UEC-TEST1 eki-D5191C21 eri-B1201B93

Images were installed from the 20100317 ISOs for AMD64.

Revision history for this message
Chuck Short (zulcss) wrote :

On lucid?

Changed in eucalyptus (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Mathias Gug (mathiaz) wrote :


Revision history for this message
Mathias Gug (mathiaz) wrote :

The CC was probably not restarted with the CLEAN=1 option set. I've updated the test case to mention the use of CLEAN=1 to restart the CC.

Changed in eucalyptus (Ubuntu):
importance: Medium → Low
status: Incomplete → Invalid
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.