Change in hostname exposition renders EC2 API unusable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Wishlist
|
Dave Walker |
Bug Description
The following commit changed the way hostnames are exposed through the EC2 API, but hides IP addresses in euca-describe-
http://
More comments from smoser on that bug:
This change makes devstack nearly unusable.
Now, a euca-describe-
$ euca-describe-
RESERVATION r-jwxxgohs 2 default
INSTANCE i-00000003 ami-00000007 server-3 server-3 running mykey 1 m1.small 2011-12-
previously, it would show:
$ euca-describe-
RESERVATION r-jwxxgohs 2 default
INSTANCE i-00000003 ami-00000007 10.0.0.4 10.0.0.4 running mykey 1 m1.small 2011-12-
The reason this is bad, is that I have no way of turning 'server-3' into
'10.0.0.4', rendering the system basically unreachable.
tags: | added: ec2 |
Changed in nova: | |
importance: | Critical → High |
Changed in nova: | |
milestone: | none → essex-rc1 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-rc1 → 2012.1 |
DescribeInstances shows two fields: privateDnsName and dnsName.
Prior to the incriminated commit, code in cloud.py would use:
privateDnsName = fixed_ip
dnsName = floating_ip or fixed_ip
With the incriminated commit, it now shows:
privateDnsName = server_name
dnsName = floating_ip or server_name
My proposed fix is to use:
privateDnsName = server_name
dnsName = floating_ip or fixed_ip
so that the (private) server name is exposed, but the IP address still shows.