public hostname get changed from internal hostname to public IP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
Low
|
Sirushti Murugesan |
Bug Description
The issue was reported by one of our users, and I've confirmed it happens when I use euca2ools. The command "euca-describe-
For example, if the public IP is 192.168.1.1, the output of euca-describe-
[ Before getting public ip ]
euca-describe-
RESERVATION r-bwadwbbb 461884eef90047f
INSTANCE i-0000088b ami-000000b4 server-2187 server-2187 running myopkey 0 m1.smal2013-
[ After getting public ip ]
euca-describe-
RESERVATION r-bwadwbbb 461884eef90047f
INSTANCE i-0000088b ami-000000b4 192.168.1.1 server-2187 running kjmac 0 m1.smal2013-
As you can see, the public hostname is changed from "server-2187" to "192.168.1.1. The user said, "it is a problem for tools that assume the public hostname is not going to change once the VM is running."
So It would be great if it can be fixed.
Our OpenStack is Essex, running on Ubuntu-12.04 hosts with VLAN Manager.
Thanks.
Changed in nova: | |
assignee: | nobody → Sirushti Murugesan (sirushtim) |
Changed in nova: | |
milestone: | none → havana-3 |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | havana-3 → 2013.2 |
I see this on folsom as well.