Comment 21 for bug 527648

Scott Moser (smoser) wrote :

I tried working around this as described above. In data center UEC at the moment:
santol (10.55.55.7): cluster-controller (CC)
cempadek (10.55.55.2): cloud-controller (CLC)

ubuntu@santol:~$ grep VNET_CLOUDIP /etc/eucalyptus/eucalyptus.local.conf
VNET_CLOUDIP=10.55.55.2

I ran 'sudo iptables -P FORWARD ACCEPT' on both CC and CLC. Then:
$ euca-run-instances --key sm-kp emi-B1E21863
$ euca-describe-instances i-3F580796
RESERVATION r-4AB408BB admin default
INSTANCE i-3F580796 emi-B1E21863 10.55.55.100 172.19.1.2 running sm-kp 0 m1.small 2010-03-01T19:18:37.335Z UEC-TEST1 eki-1E661D65 eri-F91C1CD8

The instance boots and console-output shows ec2-init ran successfully (ie, metadata service could be reached from the instance).

Now, on cempadek:
ping 10.55.55.100 succeeds
ping 172.19.1.2 fails

The instance
Maybe there was some user error, or misunderstanding, but it appears that from the CLC I can only reach the external address, not the internal. From santol (CC) either can be used.