yahoo-eng-team team mailing list archive

[Dan Smith <2033393@xxxxxxxxxxxxxxxxxx>]

The instance name in the XML is not the instance name according to nova.
It is generated based on a template by the compute driver and is not
otherwise mutable. So this is operating as designed.

** 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/2033393

Title:
  Nova does not update libvirts instance name after server rename

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  Description
  ===========

  When renaming an OpenStack instance, the change is not reflected in
  the Libvirt XML configuration, leading to inconsistency between the
  instance name in OpenStack and the name stored in the Libvirt
  configuration.

  
  Steps to reproduce
  ==================

  * Launch an instance
  * Verify the instance name is correct: virsh dumpxml instance-00xxxxxx | grep '<nova:name>'
  * Rename the instance: openstack server set --name NEW <Server-ID>
  * Check Libvirt config again

  
  Expected result
  ===============
  The instance name change should be synchronized across all components, including the underlying Libvirt configuration.

  
  Actual result
  =============
  The instance name is only changed in the database. The change is not propagated to the Libvirt configuration.

  
  Environment
  ===========

  Kolla Containers
  Version: Xena
  Hypervisor Type: Libvirt KVM

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