Sure thing.
I'm using ec2-api-tools 1.3-30349 as well.
List of commands and output:
$ ec2-run-instances -k cuec -n 1 -t c1.medium emi-BC3A13E9
RESERVATION r-480E0862 therve therve-default
INSTANCE i-3D32074E emi-BC3A13E9 0.0.0.0 0.0.0.0 pending cuec
0 c1.medium 2009-09-03T08:58:48+0000
eki-075F14CB eri-A30316F2
$ec2-describe-instances
RESERVATION r-480E0862 therve default
INSTANCE i-3D32074E emi-BC3A13E9 10.55.55.201 172.16.1.34
pending cuec 0 c1.medium 2009-09-03T08:58:48+0000
eki-075F14CB eri-A30316F2
$ date
Thu Sep 3 11:01:01 CEST 2009
This is correct for now, showing the 2 IPs.
Then I run it a couple of times, waiting a little bit after each call.
On the third attempt, I triggered the problem:
$ ec2-describe-instances
RESERVATION r-480E0862 therve default
INSTANCE i-3D32074E emi-BC3A13E9 172.16.1.34 172.16.1.34
running cuec 0 c1.medium 2009-09-03T08:58:48+0000
eki-075F14CB eri-A30316F2
$ date
Thu Sep 3 11:02:49 CEST 2009
Once it's in this state, it never shows the public IP again.
--
ec2-describe-instances sometimes shows the wrong IP
https://bugs.launchpad.net/bugs/423308
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
