← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1508753] [NEW] Handling for capitalization in protocol/action field in firewall-rule-create

 

Public bug reported:

#High level description:
Firewall Rule creation takes 2 necessary attributes:
- protocol: takes tcp, udp, icmp, any
- action: takes allow, deny ,reject
Both these take values which are Capitalization dependent.User should be given the ability to provide data in a capitalization independent way.

#Pre-conditions: None

#Step by Step reproduction:
a) Create a  firewall rule using --protocol TCP
#Expected Output:
Firewall rule created successfully when TCP is passed as an option to protocol argument.
#Actual Output:
usage: neutron firewall-rule-create [-h]
                                    [-f {html,json,json,shell,table,value,yaml,yaml}]
                                    [-c COLUMN] [--max-width <integer>]
                                    [--noindent] [--prefix PREFIX]
                                    [--request-format {json,xml}]
                                    [--tenant-id TENANT_ID] [--name NAME]
                                    [--description DESCRIPTION] [--shared]
                                    [--source-ip-address SOURCE_IP_ADDRESS]
                                    [--destination-ip-address DESTINATION_IP_ADDRESS]
                                    [--source-port SOURCE_PORT]
                                    [--destination-port DESTINATION_PORT]
                                    [--enabled {True,False}] --protocol
                                    {tcp,udp,icmp,any} --action
                                    {allow,deny,reject}
neutron firewall-rule-create: error: argument --protocol: invalid choice: u'TCP' (choose from 'tcp', 'udp', 'icmp', 'any')

# Version:
  ** OpenStack version (Specific stable branch, or git hash if from trunk): 51b2e71add3d63dccff98b22a803339e9dfae267
  ** Linux distro, kernel. For a distro, it’s also worth knowing specific versions of client and server: Ubuntu 14.04 distro
  ** DevStack or other _deployment_ mechanism? : devstack
# Environment: Single Node devstack with neutron-fwaas

* Perceived severity: Low

** Affects: python-neutronclient
     Importance: Undecided
     Assignee: Reedip (reedip-banerjee)
         Status: New


** Tags: fwaas

** Project changed: neutron => python-neutronclient

** Description changed:

- #High level description: 
+ #High level description:
  Firewall Rule creation takes 2 necessary attributes:
  - protocol: takes tcp, udp, icmp, any
  - action: takes allow, deny ,reject
  Both these take values which are Capitalization dependent.User should be given the ability to provide data in a capitalization independent way.
  
  #Pre-conditions: None
  
  #Step by Step reproduction:
  a) Create a  firewall rule using --protocol TCP
  #Expected Output:
  Firewall rule created successfully when TCP is passed as an option to protocol argument.
  #Actual Output:
  usage: neutron firewall-rule-create [-h]
-                                     [-f {html,json,json,shell,table,value,yaml,yaml}]
-                                     [-c COLUMN] [--max-width <integer>]
-                                     [--noindent] [--prefix PREFIX]
-                                     [--request-format {json,xml}]
-                                     [--tenant-id TENANT_ID] [--name NAME]
-                                     [--description DESCRIPTION] [--shared]
-                                     [--source-ip-address SOURCE_IP_ADDRESS]
-                                     [--destination-ip-address DESTINATION_IP_ADDRESS]
-                                     [--source-port SOURCE_PORT]
-                                     [--destination-port DESTINATION_PORT]
-                                     [--enabled {True,False}] --protocol
-                                     {tcp,udp,icmp,any} --action
-                                     {allow,deny,reject}
+                                     [-f {html,json,json,shell,table,value,yaml,yaml}]
+                                     [-c COLUMN] [--max-width <integer>]
+                                     [--noindent] [--prefix PREFIX]
+                                     [--request-format {json,xml}]
+                                     [--tenant-id TENANT_ID] [--name NAME]
+                                     [--description DESCRIPTION] [--shared]
+                                     [--source-ip-address SOURCE_IP_ADDRESS]
+                                     [--destination-ip-address DESTINATION_IP_ADDRESS]
+                                     [--source-port SOURCE_PORT]
+                                     [--destination-port DESTINATION_PORT]
+                                     [--enabled {True,False}] --protocol
+                                     {tcp,udp,icmp,any} --action
+                                     {allow,deny,reject}
  neutron firewall-rule-create: error: argument --protocol: invalid choice: u'TCP' (choose from 'tcp', 'udp', 'icmp', 'any')
+ 
+ # Version:
+   ** OpenStack version (Specific stable branch, or git hash if from trunk): 51b2e71add3d63dccff98b22a803339e9dfae267
+   ** Linux distro, kernel. For a distro, it’s also worth knowing specific versions of client and server: Ubuntu 14.04 distro
+   ** DevStack or other _deployment_ mechanism? : devstack
+ # Environment: Single Node devstack with neutron-fwaas
+ 
+ * Perceived severity: Low

** Changed in: python-neutronclient
     Assignee: (unassigned) => Reedip (reedip-banerjee)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1508753

Title:
  Handling for capitalization in protocol/action field in firewall-rule-
  create

Status in python-neutronclient:
  New

Bug description:
  #High level description:
  Firewall Rule creation takes 2 necessary attributes:
  - protocol: takes tcp, udp, icmp, any
  - action: takes allow, deny ,reject
  Both these take values which are Capitalization dependent.User should be given the ability to provide data in a capitalization independent way.

  #Pre-conditions: None

  #Step by Step reproduction:
  a) Create a  firewall rule using --protocol TCP
  #Expected Output:
  Firewall rule created successfully when TCP is passed as an option to protocol argument.
  #Actual Output:
  usage: neutron firewall-rule-create [-h]
                                      [-f {html,json,json,shell,table,value,yaml,yaml}]
                                      [-c COLUMN] [--max-width <integer>]
                                      [--noindent] [--prefix PREFIX]
                                      [--request-format {json,xml}]
                                      [--tenant-id TENANT_ID] [--name NAME]
                                      [--description DESCRIPTION] [--shared]
                                      [--source-ip-address SOURCE_IP_ADDRESS]
                                      [--destination-ip-address DESTINATION_IP_ADDRESS]
                                      [--source-port SOURCE_PORT]
                                      [--destination-port DESTINATION_PORT]
                                      [--enabled {True,False}] --protocol
                                      {tcp,udp,icmp,any} --action
                                      {allow,deny,reject}
  neutron firewall-rule-create: error: argument --protocol: invalid choice: u'TCP' (choose from 'tcp', 'udp', 'icmp', 'any')

  # Version:
    ** OpenStack version (Specific stable branch, or git hash if from trunk): 51b2e71add3d63dccff98b22a803339e9dfae267
    ** Linux distro, kernel. For a distro, it’s also worth knowing specific versions of client and server: Ubuntu 14.04 distro
    ** DevStack or other _deployment_ mechanism? : devstack
  # Environment: Single Node devstack with neutron-fwaas

  * Perceived severity: Low

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-neutronclient/+bug/1508753/+subscriptions