[lucid] Cloud controller fails to get detected at install-time
Bug #499098 reported by
Thierry Carrez
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_
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.
Changed in eucalyptus (Ubuntu): | |
assignee: | nobody → Thierry Carrez (ttx) |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in eucalyptus (Ubuntu): | |
status: | Triaged → 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~bzr1103- 0ubuntu4
--------------- bzr1103- 0ubuntu4) lucid; urgency=low
eucalyptus (1.6.2~
* debian/ *publication. upstart: Do not use IP address as Avahi service name, registration/ {node,walrus} : Do not include euca_conf output in log {eucalyptus- cloud,eucalyptu s-cc,uec- component- listener} .upstart: listener when both CLC and CC are running (or one
to avoid cloud/walrus conflicts (and be generally more readable), fixes
LP: #499098
* debian/
* debian/
Only start uec-component-
them is absent), fixes LP: #499367
-- Thierry Carrez <email address hidden> Tue, 22 Dec 2009 09:58:22 +0100