yahoo-eng-team team mailing list archive

[sean mooney <1989357@xxxxxxxxxxxxxxxxxx>]

nova does not supprot updating the host name in neutron via updates to the hostname of the vm.
what is actually being updated  in the tempest test is the display_name

the display name (after normalisation) is used as the initial value for the instance.hostname
instance.hostname is what is passed by nova to neutron and then read form neutron by designate.

in micoversion  2.90
hostname was added as an optional parameter to update on the server
https://docs.openstack.org/api-ref/compute/?expanded=update-server-detail#update-server

however neutron and desitnage integration was never part of that
feature.

This is an RFE not a bug and the tempest tests in https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/855870
is incorrect. i have left review feedback explaining why.

if we want to add this functionality it would require a spec

once nova has set the initial value on a port it is then not updateable
via nova.

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

Title:
  Nova doesn’t update Neutron about changing compute instance name

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  This is something that was raised on Neutron Designate DNS integration testing. 
  When VM server is created, its Nova name is used by Neutron as a hostname and then propagated to the DNS backends using Designate DNS, for example:
  https://docs.openstack.org/neutron/yoga/admin/config-dns-int-ext-serv.html#use-case-1-floating-ips-are-published-with-associated-port-dns-attributes

  Created VM is named “my_vm” and the “A” type Recordset propagated to the DNS backends is:
  my-vm.example.org. | A    | 198.51.100.4 

  Now, let’s say that the customer has decided to change VM’s name and that he would expect the previously created “A” type recordset to be change accordingly.
  Unfortunately,  such a change won’t affect either Neutron or Designate DNS, because Nova doesn’t update Neutron about changing VMs’ names.

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