[lucid] Cloud controller fails to get detected at install-time

Bug #499098 reported by Thierry Carrez
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Fix Released
Medium
Thierry Carrez

Bug Description

Installing UEC/1.6.2 with current daily.
Cloud controller IP address does not get picked up by the other components.
"euca_find_component cloud" returns nothing

This is due to a conflict in avahi service naming on a CLC+Walrus system.
Walrus runs avahi-publish -s LOCALIP, and Cloud controller does the same.

Thierry Carrez (ttx)
Changed in eucalyptus (Ubuntu):
assignee: nobody → Thierry Carrez (ttx)
importance: Undecided → Medium
status: New → Triaged
Thierry Carrez (ttx)
Changed in eucalyptus (Ubuntu):
status: Triaged → In Progress
Thierry Carrez (ttx)
Changed in eucalyptus (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package eucalyptus - 1.6.2~bzr1103-0ubuntu4

---------------
eucalyptus (1.6.2~bzr1103-0ubuntu4) lucid; urgency=low

  * debian/*publication.upstart: Do not use IP address as Avahi service name,
    to avoid cloud/walrus conflicts (and be generally more readable), fixes
    LP: #499098
  * debian/registration/{node,walrus}: Do not include euca_conf output in log
  * debian/{eucalyptus-cloud,eucalyptus-cc,uec-component-listener}.upstart:
    Only start uec-component-listener when both CLC and CC are running (or one
    them is absent), fixes LP: #499367
 -- Thierry Carrez <email address hidden> Tue, 22 Dec 2009 09:58:22 +0100

Changed in eucalyptus (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.