[Bug 1873091] [NEW] [RFE] Neutron ports dns_assignment does not match the designate DNS records for Neutron port

Launchpad Bug Tracker 1873091 at bugs.launchpad.net
Tue Sep 20 16:24:24 UTC 2022


You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

the Neutron port dns_assignment dont match the designate DNS records
assigned to the Neutron port

as explained in the link below
https://docs.openstack.org/neutron/pike/admin/config-dns-int.html

when a user creates a neutron port using the command below
neutron port-create 37aaff3a-6047-45ac-bf4f-a825e56fd2b3 \
  --dns-name my-vm --dns_domain port-domain.org.

The actual output for dns_assignment is:
{"hostname": "my-vm", "ip_address": "203.0.113.9", "fqdn": "my-vm.example.org."}
{"hostname": "my-vm", "ip_address": "2001:db8:10::9", "fqdn": "my-vm.example.org."}

and the Designate DNS records is
67a8e83d-7e3c-4fb1-9261-0481318bb7b5 | A    | my-vm.port-domain.org.  | 203.0.113.9
5a4f671c-9969-47aa-82e1-e05754021852 | AAAA | my-vm.port-domain.org.  | 2001:db8:10::9

while the expected output for dns-assignment:
{"hostname": "my-vm", "ip_address": "203.0.113.9", "fqdn": "my-vm.port-domain.org."}
{"hostname": "my-vm", "ip_address": "2001:db8:10::9", "fqdn": "my-vm.port-domain.org."}

most likely right now the dns_domain is taken from the Neutron network
dns_domain or from neutron dns_domain configuration

A good approach would be to always make the dns_assignment for Neutron
port synced with the Designate DNS records if Designate is used

=== Ubuntu SRU Details ===

[Impact]
If a network is created it assumed the dns_domain from neutron.conf if one is not provided when the network is created but if it we expect that one to take precendence. We also expect ports created on this network to use the network dns_domain. This was not happening and is fixed with this patch.

[Test Case]
* deploy Openstack Ussuri
* configure neutron-api dns-domain="test.dom1."
* create a network with --dns-domain test.dom2.
* create a vm with port on that network and check that the port is using test.dom2.

[Where things could go wrong]
This will not fix existing networks and ports but is not expected to cause any regressions.

** Affects: cloud-archive
     Importance: Undecided
         Status: New

** Affects: cloud-archive/ussuri
     Importance: Undecided
         Status: New

** Affects: cloud-archive/victoria
     Importance: Undecided
         Status: Fix Released

** Affects: neutron
     Importance: Wishlist
     Assignee: hamza (alqtaishat)
         Status: Fix Released

** Affects: neutron (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: neutron (Ubuntu Focal)
     Importance: Undecided
         Status: New


** Tags: patch rfe-approved
-- 
[RFE] Neutron ports dns_assignment does not match the designate DNS records for Neutron port
https://bugs.launchpad.net/bugs/1873091
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list