Public bug reported:
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)
** Affects: eucalyptus
Importance: High
Assignee: Daniel Nurmi (nurmi)
Status: In Progress
** Affects: eucalyptus/1.6
Importance: High
Status: In Progress
** Affects: ubuntu
Importance: Undecided
Status: New
** Changed in: eucalyptus
Status: New => In Progress
** Changed in: eucalyptus
Importance: Undecided => High
** Changed in: eucalyptus
Assignee: (unassigned) => Daniel Nurmi (nurmi)
** Also affects: ubuntu
Importance: Undecided
Status: New
** Also affects: eucalyptus/1.6
Importance: Undecided
Status: New
** Changed in: eucalyptus/1.6
Importance: Undecided => High
** Changed in: eucalyptus/1.6
Status: New => In Progress
--
Assignment of IP 169.254.169.254 on CC is conflicting with UEC avahi publish
mechanism
https://bugs.launchpad.net/bugs/449143
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
