node preseed retrieval fails due to euca_find_cluster returning 169.254.169.254
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| eucalyptus (Ubuntu) |
Fix Released
|
High
|
Dustin Kirkland | ||
Bug Description
The cluster controller's ip information looks like this:
2: eth0: <BROADCAST,
link/ether 00:16:d3:ca:e8:1e brd ff:ff:ff:ff:ff:ff
inet 10.1.1.131/24 brd 10.1.1.255 scope global eth0
inet 169.254.169.254/32 scope global eth0
inet6 fe80::216:
valid_lft forever preferred_lft forever
When avahi is asked for this system's ip address by its avahi hostname, sometimes it returns 10.1.1.131, and sometimes it returns 169.254.169.254.
Unfortunately, 169.254.169.254 isn't very useful to other nodes.
We already have some special case logic in euca_find_cluster that prefers an ipv4 address over an ipv6 address.
We need some additional logic to avoid the 169.254.169.254, and use the suggested ip address of the CC.
By "suggested IP address", a secondary change is necessary in the avahi-publish to use the $CC_IP_ADDR of the system as the "name" of the service. Previously, this was $(hostname).
:-Dustin
| Changed in eucalyptus (Ubuntu): | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Dustin Kirkland (kirkland) |
| Matt Zimmerman (mdz) wrote | #1 |
| Changed in eucalyptus (Ubuntu): | |
| status: | In Progress → Fix Committed |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in eucalyptus (Ubuntu): | |
| status: | Fix Committed → Fix Released |
> inet 169.254.169.254/32 scope global eth0
Shouldn't that be using "scope link"? I don't know if that would matter for this bug, but it seems a bit odd for it to be a global scope address. Might be harmless though.