eucalyptus node install results in broken /etc/network/interfaces

You will also want to make eth0 manual ("iface eth0 inet manual"), otherwise both the bridge and eth0 will get an IP, making the routing table funny.

Ideally, I think netcfg should make sure that netcfg/choose_interface is always set even if there's only one interface. Still, we can work around this in eucalyptus-udeb.

Etienne, can you file a separate bug about setting eth0 to manual, with more details? Dustin says he didn't have to do that and is routing table looks OK, so maybe this is a more isolated problem.

This bug was fixed in the package eucalyptus - 1.6~bzr746-0ubuntu3

---------------
eucalyptus (1.6~bzr746-0ubuntu3) karmic; urgency=low

  [ Dustin Kirkland ]
  * tools/eucalyptus-nc.in: Create the suggested 32 loop devices using
    mknod in the init script, perm'd 660, owned by root:disk, LP: #430846
  * debian/eucalyptus-udeb.finish-install: br0 needs to start at boot,
    LP: #430820

  [ Colin Watson ]
  * Work around netcfg/choose_interface not always being set (LP: #430820).
  * Actually check timeout in register_local_cloud.

  [ Mathias Gug ]
  * Recommend python-image-store-proxy for eucalyptus-cloud. The Image Store
    feature won't work without it, LP: #425926

 -- Soren Hansen <email address hidden> Wed, 16 Sep 2009 21:14:18 +0200

Colin, for me on jaunty, the following /etc/network/interfaces result in a system with broken network (ie, cannot ping or connect to anything):

-------------------------------------------
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet dhcp

auto br0
iface br0 inet dhcp
 bridge_ports eth0
-------------------------------------------

However, the following works perfectly well:

-------------------------------------------
# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet manual

auto br0
iface br0 inet dhcp
 bridge_ports eth0
-------------------------------------------

Hence, I assume having a bridge *an* one of its member interface configured for DHCP result in broken networking. Maybe I am not correct, or the behavior is different in karmic.

Attached is the output of "ip addr show" and "ip route show" with the first network config. You can see there are two default routes, etc.

I believe that Etienne is correct.

Upon installation of the Node Controller, my networking was broken until I configured eth0 to "manual", while leaving br0 to dhcp. I did, in fact, draw a dhcp address.

I'm fixing this with the following in debian/eucalyptus-udeb.finish-install:

+ sed -i "s/^iface $interface inet dhcp$/iface $interface inet manual/" /target/etc/network/interfaces

:-Dustin

This bug was fixed in the package eucalyptus - 1.6~bzr808-0ubuntu1

---------------
eucalyptus (1.6~bzr808-0ubuntu1) karmic; urgency=low

  [ Dustin Kirkland ]
  * debian/eucalyptus-udeb.finish-install: eth0 should be set to
    'manual', when configured with br0 on dhcp, LP: #430820
  * tools/euca_conf.in: ensure that /var/run/eucalyptus and
    /var/run/eucalyptus/net are created at boot and have correct
    ownerships, LP: #431114, #365349

  [ Thierry Carrez ]
  * cluster/Makefile, node/Makefile: Do not patch generated stubs if you
    didn't regenerate them, to avoid spurious build interruptions.
  * tools/eucalyptus-*.in: Do not guard initscripts basic output
    messages with VERBOSE != no (LP: #431274)
  * debian/control: Have eucalyptus-cc suggest vtun for full multi-cluster
    networking capabilities (LP: #425928)

  [ Colin Watson ]
  * Align ports used for cloud startup detection in init scripts with the
    corresponding code in euca_conf (LP: #430758).

  [ Soren Hansen ]
  * New snapshot.
  * Add a build-dependency on libc3p0-java.

 -- Soren Hansen <email address hidden> Mon, 21 Sep 2009 12:14:12 +0200