yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1989357@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

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.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: nova
-- 
Nova doesn’t update Neutron about changing compute instance name
https://bugs.launchpad.net/bugs/1989357
You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova).