Lucid UEC installer: NC doesn't publish its existence
Bug #504262 reported by
Thierry Carrez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eucalyptus (Ubuntu) |
Fix Released
|
High
|
Thierry Carrez |
Bug Description
UEC installer 20100107.1 / eucalyptus 1.6.2~bzr1120-
CLC+Walrus / CC+SC / NC topology
NC publication job doesn't run, so it never gets registered.
NC publication recently switched to started on (started ssh and started avahi-daemon and net-device-up IFACE=eth0)
However avahi-publish dies when avahi-daemon is restarted, and avahi-daemon is restarted when NC comes up (new interface added).
Pending some input from upstart experts on how to best handle the situation (supposing there is a perfect way and we are not hitting The Upstart Bug), this will be reverted to the old behavior (started on started eucalyptus-nc) which happens to work perfectly.
Changed in eucalyptus (Ubuntu): | |
assignee: | nobody → Thierry Carrez (ttx) |
importance: | Undecided → High |
status: | New → In Progress |
Changed in eucalyptus (Ubuntu): | |
status: | In Progress → Fix Committed |
To post a comment you must log in.
This bug was fixed in the package eucalyptus - 1.6.2~bzr1120- 0ubuntu6
--------------- bzr1120- 0ubuntu6) lucid; urgency=low
eucalyptus (1.6.2~
[ Thierry Carrez ] nc-publication to start on "started eucalyptus-nc", eucalyptus- nc.eucalyptus- nc-publication. upstart: Be slightly more eucalyptus- {sc,walrus} .postinst: Fix /var/lib/ eucalyptus/ .ssh
* Revert eucalyptus-
pending a more elegant solution (LP: #504262)
* debian/
accurate and start on started eucalyptus-nc, ssh and avahi-daemon.
* debian/
permissions, even for SC-only and Walrus-only installs (LP: #504309)
[ Dustin Kirkland ] eucalyptus- cloud.postinst, debian/ eucalyptus- cloud.postrm: :
* debian/
if the default "It works!" page is in place, enhance it with a redirect
to the real UEC front end, LP: #504615
-- Dustin Kirkland <email address hidden> Fri, 08 Jan 2010 00:40:59 -0600