FWaaSv2 - 'protocol' parameter is incorrect for firewall_rule

[Yushiro FURUKAWA]

If we specify 'any' as a protocol attribute when create/update firewall_rule, following error occurred:

$ openstack firewall group rule create --name myrule --protocol any

Firewall Rule protocol any is not supported. Only protocol values [None, 'tcp', 'udp', 'icmp'] and their integer representation (0 to 255) are supported.

'any' should be converted 'None' internally. In addition, help message will be updated.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/424068

[Akihiro Motoki (amotoki)]

If --protocol is not specified in firewall group rule create, users can create a rule with protocol any (None), so Medium looks an appropriate priority. Anyway let's fix it soon.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/424068
Committed: https://git.openstack.org/cgit/openstack/python-neutronclient/commit/?id=9fa08d1bd0314ac63ad7923cae1c3129c64174e3
Submitter: Jenkins
Branch: master

commit 9fa08d1bd0314ac63ad7923cae1c3129c64174e3
Author: Yushiro FURUKAWA <email address hidden>
Date: Mon Jan 23 20:22:30 2017 +0900

    FWaaSv2 - Enable to specify 'any' for protocol

    This commits fixes to specify 'any' for protocol in firewall_rule.

    Change-Id: I5d0012afdc319b67877c5ccaea4e6b41efbf6a9e
    Closes-Bug: #1658598

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/python-neutronclient 6.1.0 release.