yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxx>]

Sounds like a real bug, therefore setting the importance to "low". But
the report is pretty old, so I'm closing it. If you could reproduce this
issue on a supported release [1], please reopen this bug report.

References:
[1] http://releases.openstack.org/

** Changed in: nova
   Importance: Wishlist => Low

** Changed in: nova
       Status: Confirmed => Opinion

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

Title:
  Different instance_name_template config in controller node and compute
  node will lead to VM not be deleted actually

Status in OpenStack Compute (nova):
  Opinion

Bug description:
  If we config instance_name_template differently in controller node and
  compute node will lead to VM not be deleted in the compute node, but
  the instance is deleted in the OpenStack.

  The reason of the issue are:
  When boot instance, instance's name generated on controller node using controller's instance_name_template config and  is passed to nova-comute and used to boot a VM as VM's name.
  But When delete instance, instance's name do not pass from controller node to compute node, the instance's name is generated on compute node using compute's instance_name_template config, so the nova-compute will not find the VM to delete when compute node try to delete the VM using the instance name genenrated on compute node.

  The nova should use instance_name_template either on controller node
  or compute node, and should be consistent.

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