I haven't confirmed, but I'm matching upstream's priority of Critical.
This seems like core, broken functionality that simply must work for
Eucalyptus to be useful.
:-Dustin
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Critical
--
SYSTEM mode, clc does not send runinstances.
This was a problem with SYSTEM mode (UEC default is supposed to be
MANAGED_NOVLAN if I'm not mistaken so this shouldn't affect that). I
believe this was fixed but I need to confirm that against the upstream
(I will update this bug when I do).
--
SYSTEM mode, clc does not send runinstances.
** Changed in: eucalyptus (Ubuntu)
Status: New = Triaged
--
SYSTEM mode, clc does not send runinstances.
https://bugs.launchpad.net/bugs/430957
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Changed in: eucalyptus (Ubuntu)
Importance: Critical = High
--
SYSTEM mode, clc does not send runinstances.
https://bugs.launchpad.net/bugs/430957
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
MANAGED and MANAGED_NOVLAN work fine with revno 894.
SYSTEM mode shows the following behavior now.
The NC keeps getting run instance over and over.
cc.log
[Fri Sep 25 20:18:30 2009][019078][EUCADEBUG ] RunInstances(): called
[Fri Sep 25 20:18:30 2009][019078][EUCADEBUG ] refresh_resources():
