We've experienced a similar problem with neither the CC nor the NCs consistently discovering the public/private IP addresses of instances.
Here is how to reproduce our particular scenario: It is in SYSTEM mode and a DHCP service is running on the CC. The DHCP can assign IP addresses from many possible subnets. If a NC (that happens to have its br0 bound somewhere in, say, subnet1) starts an instance that is told by DHCP to use an IP address in subnet2, this NC's ARP table will never populate with that particular instance IP and it will go undiscovered. If the instance happens to receive an IP address on its NC's subnet, the ARP entry is set and the instance IP is discovered. (Somewhat of a) Solution: One could have all NCs bound to all subnets, but that would be a waste of IP addresses and possibly introduce routing problems. The simplest solution is to have the CC bind to all subnets, for example: "ifconfig eth0:1 <subnet2_ip> netmask ..." And just create /etc/network/interface entries so that it will persist on restarts. Since the DHCP service is on the CC, its ARP table will populate across all subnets, and the CC will always discover and report IP addresses in euca-describe-instances. However, the NCs will still show 0.0.0.0 in its nc.log, but that is acceptable for now. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/347622 Title: in SYSTEM mode, VM ips are not automatically discovered by CC or NC on switched networks To manage notifications about this bug go to: https://bugs.launchpad.net/eucalyptus/+bug/347622/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
