neutron (mitaka) rejects port updates for allowed address pairs

[George Shuklin]

Neutron 8.3 (mitaka) rejects requests to update allowed_address_pairs.

Request:

neutron --debug port-update b59bc3bb-7d34-4fbb-8e55-a9f1c5c88411 --allowed-address-pairs type=dict list=true ip_address=10.254.15.4

curl:
curl -g -i -X PUT https://network.servers.example.com:9696/v2.0/ports/b59bc3bb-7d34-4fbb-8e55-a9f1c5c88411.json -H "User-Agent: python-neutronclient" -H "Content-Type: application/json" -H "Accept: application/json" -H "X-Auth-Token: ecd92222221f2753333333c7c271788e" -d '{"port": {"allowed_address_pairs": [{"ip_address": "10.254.15.4"}]}}'

Reply:

{"NeutronError": {"message": "Unrecognized attribute(s) 'allowed_address_pairs'", "type": "HTTPBadRequest", "detail": ""}}

Log entry:

2017-01-23 09:31:58.988 28914 INFO neutron.api.v2.resource [req-56088d19-9359-4360-98db-ea9776e9dd33 46d2f76c9d5a409293cdb88ac8dcdeca 6d8ae5f32b294b2684c77417eb3b21cb - - -] update failed (client error): Unrecognized attribute(s) 'allowed_address_pairs'

[Miguel Angel Ajo (mangelajo)]

Question to the bug reporter: which plugin and configurations where you using?, ML2? ?, are you using DVR?

I have checked this on a 8.1.2 neutron deployment I have with ML2, and it worked.

So, if the report is correct this must be due to any of the patches introduced between 8.1.2 and 8.3.0 [1]

Specifically related to address pairs I only see [2], but It looks unrelated to the issue.

[1] http://paste.openstack.org/show/596098/
[2] https://review.openstack.org/#/c/328570/

[Brian Haley (brian-haley)]

Are you sure this isn't a typo? The argument to python-neutronclient is 'allowed-address-pair' without the 's' on the end.

[lavanya (g.lavanya)]

I had tried to reproduce the bug on 8.3.1 neutron(mitaka) with ML2 plugin, and it is working.

[Launchpad Janitor (janitor)]

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

[MarginHu (margin2017)]

I met this issue on Ocata version，My openstack environment use provider network, openvswitch, vlan ,the issue appeared when I disable security group, and disappeared when I enable security group.

neutron --version
6.1.0

ml2_conf.ini

[securitygroup]
firewall_driver = neutron.agent.firewall.NoopFirewallDriver
enable_security_group = false

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Bug closed due to lack of activity, please feel free to reopen if needed.