[lucid] On CLC+CC setups, uec-component-listener starts too early

Bug #499367 reported by Thierry Carrez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eucalyptus (Ubuntu)
Fix Released
High
Thierry Carrez

Bug Description

Testing 20091221.1 / eucalyptus 1.6.2~bzr1103-0ubuntu3
Walrus autoregistration fails with "CLC must be running" error.
uec-component-listener is "started on (started eucalyptus-cloud or started eucalyptus-cc)". This needs ot be slightly more subtle to handle a CC+CLC on the same machine.

Thierry Carrez (ttx)
Changed in eucalyptus (Ubuntu):
assignee: nobody → Thierry Carrez (ttx)
importance: Undecided → High
status: New → Triaged
Thierry Carrez (ttx)
Changed in eucalyptus (Ubuntu):
status: Triaged → In Progress
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: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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