DNS resolution not working in rocky, queens

Bug #1790686 reported by DevX
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack-Ansible
Fix Released
Undecided
Unassigned

Bug Description

When trying to enabling Networking service internal/external DNS resolution it does not work and results in a broken cloud. Looking at the documentation for rocky/queens it looks like the name has change and was not updated accordingly.

https://docs.openstack.org/neutron/rocky/admin/config-dns-int.html

New name is `dns_domain_ports` and not `dns` as is listed in osa.

https://github.com/openstack/openstack-ansible-os_neutron/blob/stable/rocky/templates/plugins/ml2/ml2_conf.ini.j2#L8

The following changes were added user_variables.yml
```
neutron_designate_enabled: True
neutron_dns_domain: "example.org."

neutron_plugin_base:
  - router
  - metering
  - dns
```

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to openstack-ansible-os_neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/599701

Changed in openstack-ansible:
assignee: nobody → DevX (palma-victor)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on openstack-ansible-os_neutron (master)

Change abandoned by Victor Palma (<email address hidden>) on branch: master
Review: https://review.openstack.org/599701
Reason: According to documentation DNS is still available if needed I can provide another patch that add dns domain ports.

Revision history for this message
Georgina Shippey (gshippey) wrote :

Fix released and backported to Rocky.
https://review.opendev.org/#/c/624097/

Changed in openstack-ansible:
assignee: DevX (palma-victor) → nobody
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.