yahoo-eng-team team mailing list archive

[Lucas Kanashiro <1989357@xxxxxxxxxxxxxxxxxx>]

I added a task for sssd here to not miss this other bug report which is
a dup of this one (#1989358). However, I am not sure how sssd is
involved on this issue. Please, provide more information and detailed
steps on how to reproduce the issue.

** Also affects: sssd (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: sssd (Ubuntu)
       Status: New => Incomplete

-- 
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):
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete

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