Comment 7 for bug 458904

After more investigation it turns out that the problem lies with the avahi resolver. Whenever a new public IP address (for an instance) is added to the CC, avahi-daemon will publish it automatically.

Subsequent installs will use one of the publish IP by avahi daemon (which turns out to be the last IP added to the public network interface). euca_find_cluser uses avahi dns resolution to get the CC IP address to get the seed from and will only use the published IP by the CC avahi publication job if the resolution leads to

The proposed workaround is to always use the IP publish by the CC publication job.