This issue is now being tracked upstream at
http://eucalyptus.atlassian.net/browse/EUCA-2638
Please watch that issue for further updates.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
Targeting this bug for milestone 2.0.4: we probably need to document
this, since we cannot bind to subnet we are not aware exists.
** Changed in: eucalyptus
Milestone: None = 2.0.4
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Also dropping importance since the original issue was resolved: we just
need to document the multi-subnet behavior.
** Changed in: eucalyptus
Status: Fix Committed = In Progress
** Changed in: eucalyptus
Importance: High = Low
** Changed in: eucalyptus
Assignee: Daniel Nurmi
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
It seems that this still isn't resolved. We're running Ubuntu 10.04
Enterprise Cloud and our scenario fits this one perfectly.
--
uecad...@cloudnc:~$ uname -a
Linux cloudnc 2.6.32-21-generic-pae #32-Ubuntu SMP Fri Apr 16 09:39:35 UTC 2010
i686 GNU/Linux
Still not working under jaunty :(
r...@x-dom0-01:/etc/eucalyptus# dpkg -l|grep iptables
ii iptables 1.4.1.1-4ubuntu3
administration tools for packet filtering an
r...@x-dom0-01:/etc/eucalyptus# dpkg -l|grep eucalyptus
ii eucalyptus-common
