[Bug 476619] [NEW] Networking problem in Eucalyptus when VNET_PUBLICIPS has an IP being used in its range
etienne.goyer at canonical.com
Fri Nov 6 16:04:34 GMT 2009
Public bug reported:
This was reported to me by a third-party, and I have not verified or
reproduced the problem myself. Also, I understand it is a user error,
but I think we should have some safeguard against it, as it is an easy
one to make.
If the VNET_PUBLICIPS directive include an IP that is being used by the
CC, networking will get very get wonky when that IP is attributed to an
instance. For example, given a frontend (CC) that as an IP of
192.168.1.100 for eth0 (it's "public" interface), if you have
/etc/eucalyptus/eucalyptus.conf (that could happen, for example, if you
provided that range during the installation), then Eucalyptus will
assign 192.168.1.100 as public IP for the first instance to be run, and
then neither the instance nor the frontend will be reachable from the
network. Inspecting the output of ifconfig, you will notice that both
eth0 and eth0:publics interfaces have 192.168.1.100 as an IP, which is
probably what broke networking on the frontend.
Best would be for Eucalyptus to actually check for that condition and
not assign an IP that is in use by the CC to an instance.
** Affects: eucalyptus (Ubuntu)
Networking problem in Eucalyptus when VNET_PUBLICIPS has an IP being used in its range
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
More information about the Ubuntu-server-bugs