yahoo-eng-team team mailing list archive

[Edward Hope-Morley <1989986@xxxxxxxxxxxxxxxxxx>]

By extension, the ovn dns entries are also not updated if I set/change
domain on the network itself:

$ openstack network set --dns-domain "testlab2.stsstack.qa.1ss." private
$ openstack network show private -c dns_domain -f value
testlab2.stsstack.qa.1ss.

New networks do get the correct domain. Looks like this might actually
be a neutron bug then.

** Also affects: neutron
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1989986

Title:
  changing dns_domain on the charm does not propagate to ovn

Status in OpenStack Neutron API Charm:
  New
Status in neutron:
  New

Bug description:
  If I deploy Focal Ussuri with the Openstack charms and set a domain on
  the neutron-api dns-domain config and then subsequently change it to
  another value, the dns table entries in ovn-central do not get updated
  i.e.

  # ovn-nbctl list dns
  _uuid               : 9ed2e4db-e262-4745-9c5b-0d808269431d
  external_ids        : {ls_name=neutron-a193dccd-1e21-4ee3-be93-a88e86f0d2c4}
  records             : {"160.21.168.192.in-addr.arpa"=focal-124153.testlab.stsstack.qa.1ss, focal-124153="192.168.21.160", focal-124153.testlab.stsstack.qa.1ss="192.168.21.160"}

  should be using domain "testlab2.stsstack.qa.1ss" since that is what I
  set on the charm and is set in the config:

  # grep -r dns /etc/neutron/neutron.conf 
  dns_domain = testlab2.stsstack.qa.1ss.

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-neutron-api/+bug/1989986/+subscriptions