yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => havana-3

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1096468

Title:
  public hostname get changed from internal hostname to public IP

Status in OpenStack Compute (Nova):
  Fix Released

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-instances"
  shows internal hostname as public hostname until the instance gets a
  public IP.

  For example, if the public IP is 192.168.1.1, the output of euca-
  describe-instances will change like this.

  [ Before getting public ip ]
  euca-describe-instances i-0000088b
  RESERVATION	r-bwadwbbb	461884eef90047fbb4eb9ec92f22a1e3	default
  INSTANCE	i-0000088b	ami-000000b4	server-2187	server-2187	running	myopkey	0		m1.smal2013-01-05T21:09:31.000Z	india	aki-000000b3			monitoring-disabled	10.1.2.133	10.1.2.133	instance-store

  [ After getting public ip ]
  euca-describe-instances i-0000088b
  RESERVATION	r-bwadwbbb	461884eef90047fbb4eb9ec92f22a1e3	default
  INSTANCE	i-0000088b	ami-000000b4	192.168.1.1	server-2187	running	kjmac	0		m1.smal2013-01-05T21:09:31.000Z	india	aki-000000b3			monitoring-disabled	 192.168.1.1 	10.1.2.133	instance-store

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1096468/+subscriptions