yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #62901
[Bug 1669467] Re: security-groups rule add does not handle "any" protocol or port (while neutron allows it)
Reviewed: https://review.openstack.org/440621
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=87337ff255b581a57809e7ea9d901c00b3514d45
Submitter: Jenkins
Branch: master
commit 87337ff255b581a57809e7ea9d901c00b3514d45
Author: Yves-Gwenael Bourhis <yves-gwenael.bourhis@xxxxxxxxxxxxx>
Date: Thu Mar 2 16:13:18 2017 +0100
Allow any port or protocol in security group rules
Neutron allows setting port or protocol wildcard by not specifying any value
for them.
Example, these are allowed by neutron:
neutron security-group-rule-create --direction egress <sgid>
neutron security-group-rule-create --direction egress --protocol tcp <sgid>
Specifying '-1' for IP protocol means a wildcard IP protocol.
validate_ip_protocol is updated accordingly.
'All ports' choice is added to 'Open Port' field.
Change-Id: I4a7262eda89e3206c743fee14c78aa6b49308ce6
Closes-Bug: 1669467
** Changed in: horizon
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1669467
Title:
security-groups rule add does not handle "any" protocol or port (while
neutron allows it)
Status in OpenStack Dashboard (Horizon):
Fix Released
Bug description:
Neutron allows setting port or protocol wildcard by not specifying any
value for them.
example, these are allowed by neutron :
neutron security-group-rule-create --direction egress <sec_group_id>
neutron security-group-rule-create --direction egress --protocol tcp <sec_group_id>
Currently horizon refuses not specifying a port and does not mention that we can leave the protocol field empty as a wildcard. Meaning that the above commands can not be performed via horizon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1669467/+subscriptions
References