This bug was fixed in the package eucalyptus - 1.6~bzr746-0ubuntu1
---
eucalyptus (1.6~bzr746-0ubuntu1) karmic; urgency=low
* New upstream, bugfix snapshot.
* Add more full-featured default network configuration (LP: #425914).
-- Soren HansenTue, 15 Sep 2009 13:50:40 +0200
soren: so what can go wrong here? Eucalyptus packages failing to
configure in cases where it configured before (e.g., if the admin provides no
input on the new debconf questions)? Things breaking on upgrade?
slangasek: This only applies for fresh installs.
slangasek: The primary risk is the
In SYSTEM mode, Eucalypus connects instances to the existing LAN by way
of a bridge, and relies on existing networking infrastructure (DHCP
servers, DNS, etc.) to run them. This is a very basic mode of operation,
and is somewhat limited. In MANAGED(-NOVLAN) you get all the bells and
whistles Eucaly
To evaluate this for a freeze exception, we need to understand what the
risks are of this change - what is it about this change thta makes it
more than a simple bugfix?
--
[FFe] CC and NC networking mode is set to 'SYSTEM' by default
https://bugs.launchpad.net/bugs/425914
You received this bug no
** Changed in: eucalyptus (Ubuntu)
Status: Triaged => New
--
[FFe] CC and NC networking mode is set to 'SYSTEM' by default
https://bugs.launchpad.net/bugs/425914
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
** Branch linked: lp:~soren/eucalyptus/ubuntu.networking-defaults
--
[FFe] CC and NC networking mode is set to 'SYSTEM' by default
https://bugs.launchpad.net/bugs/425914
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
** Summary changed:
- CC and NC networking mode is set to 'SYSTEM' by default
+ [FFe] CC and NC networking mode is set to 'SYSTEM' by default
--
[FFe] CC and NC networking mode is set to 'SYSTEM' by default
https://bugs.launchpad.net/bugs/425914
You received this bug notification because you are