yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1269851@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

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

Title:
  Allowed Address Pair Extension doesn't work with port update

Status in neutron:
  Expired

Bug description:
  When doing a port update (put) specifying the allowed address pair
  attribute, the api returns a 200, but the attribute is not actually
  updated. An example from a Tempest test run follows:

  1) The following request was executed:

  Request: PUT http://172.16.0.2:9696//v2.0/ports/cd09c39c-a0b1-41ee-8071-1025f6b643ee
  Request Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 'X-Auth-Token': '<Token omitted>'}
  Request Body: {"port": {"name": "new-port-name-tempest-1616712189", "allowed_address_pairs": [{"ip_address": "10.0.0.4", "mac_address": "fa:16:3e:ac:db:b8"}]}}

  2) The api responded with:

  Response Status: 200
  Response Headers: {'date': 'Tue, 07 Jan 2014 10:19:05 GMT', 'content-length': '577', 'content-type': 'application/json; charset=UTF-8', 'connection': 'close'}
  Response Body: {"port": {"status": "ACTIVE", "name": "new-port-name-tempest-1616712189", "allowed_address_pairs": [], "admin_state_up": true, "network_id": "65873dcd-31b7-4d4d-b49e-6d07e790a83e", "tenant_id": "d5202d6925954430a2ae691d2919067f", "extra_dhcp_opts": [], "device_owner": "compute:None", "mac_address": "fa:16:3e:cf:2f:8b", "fixed_ips": [{"subnet_id": "41cca890-3197-4837-9242-add4d6ac2e49", "ip_address": "10.0.0.3"}], "id": "cd09c39c-a0b1-41ee-8071-1025f6b643ee", "security_groups": ["8800c2bb-8fb5-4d23-bdc3-cc162a56d1c6"], "device_id": "1ebf20b7-4494-4784-b3d3-f27df6de2f31"}}

  As can be seen in this response, the "allowed_address_pairs" attribute
  was not modified, even though the response status was 200

  3) Further proof that the  "allowed_address_pairs" attribute was not
  modified comes from a show port:

  Request: GET http://172.16.0.2:9696//v2.0/ports/cd09c39c-a0b1-41ee-8071-1025f6b643ee
  Request Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 'X-Auth-Token': '<Token omitted>'}
  Response Status: 200
  Response Headers: {'content-length': '577', 'content-location': u'http://172.16.0.2:9696//v2.0/ports/cd09c39c-a0b1-41ee-8071-1025f6b643ee', 'date': 'Tue, 07 Jan 2014 10:19:05 GMT', 'content-type': 'application/json; charset=UTF-8', 'connection': 'close'}
  Response Body: {"port": {"status": "ACTIVE", "name": "new-port-name-tempest-1616712189", "allowed_address_pairs": [], "admin_state_up": true, "network_id": "65873dcd-31b7-4d4d-b49e-6d07e790a83e", "tenant_id": "d5202d6925954430a2ae691d2919067f", "extra_dhcp_opts": [], "device_owner": "compute:None", "mac_address": "fa:16:3e:cf:2f:8b", "fixed_ips": [{"subnet_id": "41cca890-3197-4837-9242-add4d6ac2e49", "ip_address": "10.0.0.3"}], "id": "cd09c39c-a0b1-41ee-8071-1025f6b643ee", "security_groups": ["8800c2bb-8fb5-4d23-bdc3-cc162a56d1c6"], "device_id": "1ebf20b7-4494-4784-b3d3-f27df6de2f31"}}

  As can be seen in the response, the "allowed_address_pairs" attribute
  is an empty list

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