Failed to create network or port with dns_domain parameter

[Slawek Kaplonski]

When I had enabled in ML2 extension drivers: "subnet_dns_publish_fixed_ip" and "dns" then I wasn't able to create network or port with dns-domain attribute.

Creation of network:

neutron net-create test-net-1 --dns-domain test.domain.
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
Failed to create a duplicate NetworkDNSDomain: for attribute(s) ['PRIMARY'] with value(s) 26cd2031-e611-4c4c-b07d-cff23d12a952
Neutron server returns request_ids: ['req-abb4798b-f79a-472d-b936-ae8edcccfb6d']

And the result in the server logs: http://paste.openstack.org/show/795750/

Creation of port:

neutron port-create test-net-1 --dns-domain test.domain.
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
Failed to create a duplicate PortDNS: for attribute(s) ['PRIMARY'] with value(s) 1d7544bd-3a16-4c0f-b67f-af99db6069a5
Neutron server returns request_ids: ['req-5db9dab8-7800-4e61-8fd7-72149861bd25']

And the result in the server logs: http://paste.openstack.org/show/795751/

Creation of port or network without dns-domain and then setting it via PUT request works fine.

When I have only one of those 2 extensions enabled, all works fine also.

[Dr. Jens Harbott (j-harbott)]

It is an error to have two of the dns extensions enabled at the same time, only enable the one that has all the features that you need, in this case subnet_dns_publish_fixed_ip, this will include the dns extension automatically. I had the similar issue while developing the extenstion but after discussing with mlavalle about how this could be handled, the solution was to only have one of them active at a time.

[Maciej Jozefczyk (maciejjozefczyk)]

I can confirm this particular issue. I remember having the same, while two DNS extensions were enabled on same time trying to add same value withing same API operation to the DB.

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Hello:

IMO, we can:
- Include a note in both API docs.
- We can implement a mechanism to, according to the extension configuration, supersede a previous loaded extension. In this case, for example, "subnet-dns-publish-fixed-ip" will supersede "dns".
- Make inherited methods from SubnetDNSPublishFixedIPExtensionDriver re-entrant. But personally I don't like this idea and I think the second option is cleaner.

Regards.