Assignment of IP 169.254.169.254 on CC is conflicting with UEC avahi publish mechanism
Bug #449143 reported by
Daniel Nurmi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Eucalyptus |
Fix Released
|
High
|
Daniel Nurmi | ||
1.6 |
Fix Released
|
High
|
Unassigned | ||
eucalyptus (Ubuntu) |
Fix Released
|
Medium
|
Thierry Carrez |
Bug Description
In the UEC, the CC uses avahi-publish to announce the existence of a cluster on the network. If the CC is registered, however, it will add the 169.254.169.254 address to the local interface, and for reasons we cannot determine, this interferes with avahi-publish to the point where nodes cannot see the published service using 'avahi-browse -at' any longer.
We're considering a fix in Eucalyptus itself whereby we restrict the 169.254.169.254 assignment to be link-local, which allows the avahi-publish to function again (we're assuming that avahi-publish is only choosing globally scoped subnets to broadcast on?)
This fix is in testing now (Oct11/2009)
Changed in eucalyptus: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Daniel Nurmi (nurmi) |
affects: | ubuntu → eucalyptus (Ubuntu) |
Changed in eucalyptus: | |
status: | In Progress → Fix Committed |
Changed in eucalyptus (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in eucalyptus (Ubuntu): | |
assignee: | nobody → Thierry Carrez (ttx) |
status: | Triaged → In Progress |
Changed in eucalyptus: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fixed in revno 925