announces cc and sc to wrong network

[Christoph Martin]

I installed eucalyptus clc and walrus on a host with public network and then cc and sc on a host with both public and private network. The installation asked wether I want to use eth1 as private network to connect to the nc's and I answerd yes. But now cc and nc get published via avahi with their public IP address and not with the private IP address.

The consequense is that the node controller installed on the private network will try to connect the cc and sc with the wrong IP and will fail.

The problem is, that /etc/eucalyptus/eucalyptus-ipaddr.conf tries to find out the IP address by checking the default route. But in this setup the default route is via the public interface.

It should take the value of VNET_PRIVINTERFACE in /etc/eucalyptus/eucalyptus.conf to find out the correct interface and ip address.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: eucalyptus-cc 2.0+bzr1241-0ubuntu4.1
ProcVersionSignature: Ubuntu 2.6.35-27.48-server 2.6.35.11
Uname: Linux 2.6.35-27-server x86_64
NonfreeKernelModules: mptspi mptscsih mptbase e1000 floppy megaraid_mbox megaraid_mm
.etc.eucalyptus.eucalyptus.cc.conf: CC_NAME="cluster1"
Architecture: amd64
Date: Fri Apr 1 10:37:23 2011
InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: eucalyptus

[Dave Walker (davewalker)]

Thanks for the bug report Christoph. It may be too late in the Natty cycle to addresses this issue for the next release, but we wil certainly investigate. Thanks!