Reviewed: https://review.openstack.org/511561
Committed:
https://git.openstack.org/cgit/openstack/neutron/commit/?id=7ff492c5bb9ce9f24f12db40c8e3a33beb47f87b
Submitter: Zuul
Branch: master
commit 7ff492c5bb9ce9f24f12db40c8e3a33beb47f87b
Author: Brian Haley <bha...@redhat.com>
Date: Thu Oct 12 15:25:26 2017 -0400
Support protocol numbers in security group API
Somewhere along the way we broke supporting numbers in
the security group API that were not in our known list
of protocols. In order to fix this properly we must
use the correct arguments when using iptables-save, as
it could use a name instead of a number, or vice-versa.
Determined the list of mappings by doing:
for num in {0..255}; do iptables -A INPUT -p $num; done
# iptables-save
Change-Id: I5895250b47ddf664d214cf085be693c3897e0c87
Closes-bug: #1716045
Closes-bug: #1716790
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1716790
Title:
Security Group specifying protocol 0 results in Error 400
Status in neutron:
Fix Released
Bug description:
Per the documentation protocol 0 should be allowed (not sure what it
does? Accept any protocol? Test?). However it results in a 400 error.
Neutron should accept 0.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1716790/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
