yahoo-eng-team team mailing list archive

[George Shuklin <1467518@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

neutron --debug port-list --binding:vif_type=binding_failed displays all
ports with all vif_type, not only with binding_failed.

vif_type=binding_failed is set when something bad happens on a compute
host during port configuration (no local vlans in ml2 conf, etc)

We had intention to monitor for such ports, but request to neutron
return some irrelevant ports:

REQ: curl -i -X GET
https://neutron.lab.internal:9696/v2.0/ports.json?binding%3Avif_type=binding_failed
-H "User-Agent: python-neutronclient" -H "Accept: application/json" -H
"X-Auth-Token: 52c0c1ee1f764c408977f41c9f3743ca"

RESP BODY: {"ports": [{"status": "ACTIVE", "binding:host_id":
"compute2", "name": "", "admin_state_up": true, "network_id": "5c399fb7
-67ac-431d-9965-9586dbcec1c9", "tenant_id":
"3e6b1fc20da346838f93f124cb894d0f", "extra_dhcp_opts": [],
"binding:vif_details": {"port_filter": false, "ovs_hybrid_plug": false},
"binding:vif_type": "ovs", "device_owner": "network:dhcp",
"mac_address": "fa:16:3e:ad:6f:22", "binding:profile": {},
"binding:vnic_type": "normal", "fixed_ips": [{"subnet_id":
"c10a3520-17e2-4c04-94c6-a4419d79cca9", "ip_address": "192.168.0.3"}],
.....

If request is send on neutron --debug port-list
--binding:host_id=compute1, filtering works as expected.

Neutron version - 2014.2.4

** Affects: neutron
     Importance: Undecided
         Status: New

** Summary changed:

- neutron --debug port-list --binding:vif_type=binding_failed displays wrong ports
+ neutron --debug port-list --binding:vif_type=binding_failed returns wrong ports

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1467518

Title:
  neutron --debug port-list --binding:vif_type=binding_failed returns
  wrong ports

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  neutron --debug port-list --binding:vif_type=binding_failed displays
  all ports with all vif_type, not only with binding_failed.

  vif_type=binding_failed is set when something bad happens on a compute
  host during port configuration (no local vlans in ml2 conf, etc)

  We had intention to monitor for such ports, but request to neutron
  return some irrelevant ports:

  REQ: curl -i -X GET
  https://neutron.lab.internal:9696/v2.0/ports.json?binding%3Avif_type=binding_failed
  -H "User-Agent: python-neutronclient" -H "Accept: application/json" -H
  "X-Auth-Token: 52c0c1ee1f764c408977f41c9f3743ca"

  RESP BODY: {"ports": [{"status": "ACTIVE", "binding:host_id":
  "compute2", "name": "", "admin_state_up": true, "network_id":
  "5c399fb7-67ac-431d-9965-9586dbcec1c9", "tenant_id":
  "3e6b1fc20da346838f93f124cb894d0f", "extra_dhcp_opts": [],
  "binding:vif_details": {"port_filter": false, "ovs_hybrid_plug":
  false}, "binding:vif_type": "ovs", "device_owner": "network:dhcp",
  "mac_address": "fa:16:3e:ad:6f:22", "binding:profile": {},
  "binding:vnic_type": "normal", "fixed_ips": [{"subnet_id":
  "c10a3520-17e2-4c04-94c6-a4419d79cca9", "ip_address": "192.168.0.3"}],
  .....

  If request is send on neutron --debug port-list
  --binding:host_id=compute1, filtering works as expected.

  Neutron version - 2014.2.4

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