yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

Renaming the instance is just updating the instances.display_name column
in the database, it's not actually rename the internal instance.name
value which is generated based on the CONF.instance_name_template config
option and is used to set the initial hostname of the guest.  So
basically, updating the name is just the display name, it doesn't rename
the hostname in the guest.

** Changed in: nova
       Status: New => Invalid

-- 
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/1566673

Title:
  hostname is not renamed

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  After deployed with agent_ssh driver, when rename instance name, host
  name is not renamed.

  $ nova list
  +--------------------------------------+-------------+--------+------------+-------------+-----------------------------------------------------+
  | ID                                   | Name        | Status | Task State | Power State | Networks                                            |
  +--------------------------------------+-------------+--------+------------+-------------+-----------------------------------------------------+
  | c9f406c6-d920-4ab6-bae8-309897b3c1ad | test-agent1 | ACTIVE | -          | Running     | private=fd03:122:f6d1:0:5054:ff:fee5:4c04, 10.0.0.4 |
  +--------------------------------------+-------------+--------+------------+-------------+-----------------------------------------------------+

  $ ssh ubuntu@10.0.0.4
  ubuntu@test-agent1:~$

  $ nova update c9f406c6-d920-4ab6-bae8-309897b3c1ad --name test-agent2

  $ nova list
  +--------------------------------------+-------------+--------+------------+-------------+-----------------------------------------------------+
  | ID                                   | Name        | Status | Task State | Power State | Networks                                            |
  +--------------------------------------+-------------+--------+------------+-------------+-----------------------------------------------------+
  | c9f406c6-d920-4ab6-bae8-309897b3c1ad | test-agent2 | ACTIVE | -          | Running     | private=fd03:122:f6d1:0:5054:ff:fee5:4c04, 10.0.0.4 |
  +--------------------------------------+-------------+--------+------------+-------------+-----------------------------------------------------+

  $ ssh ubuntu@10.0.0.4
  ubuntu@test-agent1:~$

  It's same in case of using libvirt driver, not Ironic driver. Is this
  correct behavior?

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