yahoo-eng-team team mailing list archive

[Anton Kurbatov <2109354@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I encountered an issue where the number of returned networks is unexpected when combining a provider:network_type filter with the limit parameter.
For example, if there are 2 VLAN networks, filtering with provider:network_type=vlan&limit=2 returns only 1 network.

To reproduce the issue, you can create 2–3 VXLAN networks, 1 flat
network, and 2–3 VLAN networks.

Demo setup:
public is a flat network
vlan100 and vlan200 are VLAN networks
private and lb-mgmt-net are VXLAN networks


[root@akdev0 ~]# openstack network list
+--------------------------------------+-------------+--------------------------------------+
| ID                                   | Name        | Subnets                              |
+--------------------------------------+-------------+--------------------------------------+
| 4bf7c66f-9ea4-4fd0-89a4-0d272473ecee | vlan100     |                                      |
| 5884d655-7411-4c6e-9d02-9c7309eb8d23 | public      | b553c7c6-9b18-4bff-b8cd-f8c162430b04 |
| 9697e747-7cd8-4b38-8d2a-ad94a05d3588 | vlan200     |                                      |
| dd218645-bab7-4228-9964-b0f2e55803c8 | private     | b69faa93-f668-4287-853b-665b8771642b |
| f840476c-bc9e-434c-aa66-869ce9fdf93a | lb-mgmt-net | f9ba96b6-22f9-4297-a59b-62066f877989 |
+--------------------------------------+-------------+--------------------------------------+
[root@akdev0 ~]# curl -ks -H "x-auth-token: $(openstack token issue -c id -f value)" "http://10.136.20.79:9696/networking/v2.0/networks?provider%3Anetwork_type=vlan&limit=1"; | jq .networks[].id
"4bf7c66f-9ea4-4fd0-89a4-0d272473ecee"
[root@akdev0 ~]# curl -ks -H "x-auth-token: $(openstack token issue -c id -f value)" "http://10.136.20.79:9696/networking/v2.0/networks?provider%3Anetwork_type=vlan&limit=2"; | jq .networks[].id
"4bf7c66f-9ea4-4fd0-89a4-0d272473ecee"
[root@akdev0 ~]# curl -ks -H "x-auth-token: $(openstack token issue -c id -f value)" "http://10.136.20.79:9696/networking/v2.0/networks?provider%3Anetwork_type=vlan&limit=3"; | jq .networks[].id
"4bf7c66f-9ea4-4fd0-89a4-0d272473ecee"
"9697e747-7cd8-4b38-8d2a-ad94a05d3588"
[root@akdev0 ~]#

** 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/2109354

Title:
  Incorrect behavior when filtering networks by provider:network_type
  with a limit parameter

Status in neutron:
  New

Bug description:
  I encountered an issue where the number of returned networks is unexpected when combining a provider:network_type filter with the limit parameter.
  For example, if there are 2 VLAN networks, filtering with provider:network_type=vlan&limit=2 returns only 1 network.

  To reproduce the issue, you can create 2–3 VXLAN networks, 1 flat
  network, and 2–3 VLAN networks.

  Demo setup:
  public is a flat network
  vlan100 and vlan200 are VLAN networks
  private and lb-mgmt-net are VXLAN networks

  
  [root@akdev0 ~]# openstack network list
  +--------------------------------------+-------------+--------------------------------------+
  | ID                                   | Name        | Subnets                              |
  +--------------------------------------+-------------+--------------------------------------+
  | 4bf7c66f-9ea4-4fd0-89a4-0d272473ecee | vlan100     |                                      |
  | 5884d655-7411-4c6e-9d02-9c7309eb8d23 | public      | b553c7c6-9b18-4bff-b8cd-f8c162430b04 |
  | 9697e747-7cd8-4b38-8d2a-ad94a05d3588 | vlan200     |                                      |
  | dd218645-bab7-4228-9964-b0f2e55803c8 | private     | b69faa93-f668-4287-853b-665b8771642b |
  | f840476c-bc9e-434c-aa66-869ce9fdf93a | lb-mgmt-net | f9ba96b6-22f9-4297-a59b-62066f877989 |
  +--------------------------------------+-------------+--------------------------------------+
  [root@akdev0 ~]# curl -ks -H "x-auth-token: $(openstack token issue -c id -f value)" "http://10.136.20.79:9696/networking/v2.0/networks?provider%3Anetwork_type=vlan&limit=1"; | jq .networks[].id
  "4bf7c66f-9ea4-4fd0-89a4-0d272473ecee"
  [root@akdev0 ~]# curl -ks -H "x-auth-token: $(openstack token issue -c id -f value)" "http://10.136.20.79:9696/networking/v2.0/networks?provider%3Anetwork_type=vlan&limit=2"; | jq .networks[].id
  "4bf7c66f-9ea4-4fd0-89a4-0d272473ecee"
  [root@akdev0 ~]# curl -ks -H "x-auth-token: $(openstack token issue -c id -f value)" "http://10.136.20.79:9696/networking/v2.0/networks?provider%3Anetwork_type=vlan&limit=3"; | jq .networks[].id
  "4bf7c66f-9ea4-4fd0-89a4-0d272473ecee"
  "9697e747-7cd8-4b38-8d2a-ad94a05d3588"
  [root@akdev0 ~]#

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2109354/+subscriptions