
The openstack client changes the protocol to None in the case that 'any' is given as an argument when creating a security group rule. But using 'any' in a POST call will return an error saying it is invalid. Add special treatment for 'any' as a protocol value in the API by treating it the same as None, but do not use the 'any' string when creating the DB entry, it is only treated as an alias. Closes-bug: #2074056 Change-Id: Ic88ae2c249eb2cd1af1ebbf6707c707f51a52638
9 lines
390 B
YAML
9 lines
390 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Add special treatment for the keyword ``any`` in the security group rule
|
|
API protocol field to match what is documented in the api-ref itself.
|
|
It is already supported in the client, where ``any`` is simply changed
|
|
to ``None``, so do the same in the API itself. For more information,
|
|
see bug `2074056 <https://bugs.launchpad.net/neutron/+bug/2074056>`_.
|