← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1669467] [NEW] security-groups rule add does not handle "any" protocol or port (while neutron allows it)

 

Public bug reported:

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.

** Affects: horizon
     Importance: Undecided
     Assignee: Yves-Gwenael Bourhis (yves-gwenael-bourhis)
         Status: In Progress

-- 
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):
  In Progress

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


Follow ups