Network filtering by dns_domain is not supported in the "dns-integration" extension

Bug #1818318 reported by kay on 2019-03-02
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Medium
Unassigned

Bug Description

Filtering network by "dns_domain" (http://neutron/v2.0/networks?dns_domain=foo) returns:

in_() not yet supported for relationships. For a simple many-to-one, use in_() against the set of foreign key values.

However ports filtering by dns_name works fine (in Neutron Mitaka):

http://neutron/v2.0/ports?dns_name=bar

Floating IPs filtering by dns_name or dns_domain also doesn't work (filter is just not applied) and Neutron (even in Mitaka) returns all floating IPs.

I haven't managed to clarify why.

kay (kay-diam) on 2019-03-02
Changed in neutron:
status: New → Invalid
kay (kay-diam) on 2019-03-04
Changed in neutron:
status: Invalid → New
kay (kay-diam) wrote :

Another issue with DNS filtering. Looks like the Neutron Mitaka is capable to filter _ports_ by "dns_name", but the Neutron Queens returns all the ports.

kay (kay-diam) on 2019-03-04
description: updated
kay (kay-diam) on 2019-03-04
description: updated
Changed in neutron:
importance: Undecided → Medium
kay (kay-diam) wrote :

Any news on this?

kay (kay-diam) wrote :

Do you have any news on this issue? It broke automation once neutron was upgrade from mitaka to queens.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers