This bug was fixed in the package eucalyptus - 1.6.2~bzr1136-0ubuntu3
---------------
eucalyptus (1.6.2~bzr1136-0ubuntu3) lucid; urgency=low
* eucalyptus-cc.eucalyptus-cc-publication.upstart,
eucalyptus-common.eucalyptus.upstart, eucalyptus-network.upstart,
eucalyptus-sc.eucalyptus-sc-publication.upstart,
eucalyptus-walrus.eucalyptus-walrus-publication.upstart, rules: rework
our eucalyptus starting condition to depend on a new upstart emitted
signal, eucalyptus-network-is-ready, which is only fired once the
network interface providing the default route is in fact up, and
listening on a real ip address, LP: #503180
* debian/eucalyptus-common.eucalyptus.upstart:
- don't respawn eucalyptus-cloud
- ensure that the iptables module gets loaded soon enough, otherwise
much bad behavior happens in various nasty ways, most notably, a
wedged database which renders the CLC non responsive on restart/reboot,
LP: #503180 and dupes, LP: #444352, #444946, #467521, #478573, #480048
-- Dustin Kirkland <kirkl...@ubuntu.com> Tue, 02 Feb 2010 17:13:52 -0800
** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Confirmed => Fix Released
--
eucalyptus-cloud doesn't reply to requests (eucalyptus doesn't work after
reboot or services restart issues due to upstart networking behavior)
https://bugs.launchpad.net/bugs/503180
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
