← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1651420] Re: Can not clear source or dest port (range) for existing firewall rule

 

Bug closed due to lack of activity, please feel free to reopen if
needed.

** Changed in: neutron
       Status: Incomplete => Won't Fix

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

Title:
  Can not clear source or dest port  (range)  for existing firewall rule

Status in neutron:
  Won't Fix

Bug description:
  We need to give user a way to update firewall rule to clear source or
  dest port (range).

  We can create a firewall-rule with source-ip-address and destination-ip-address set, for example:
  [root@node-1 ~]# neutron firewall-rule-create --source-ip-address 0.0.0.0/0 --source-port 1234 --destination-ip-address 192.168.2.0/24 --destination-port 22 --protocol tcp --action allow
  Created a new firewall_rule:
  +------------------------+--------------------------------------+
  | Field                  | Value                                |
  +------------------------+--------------------------------------+
  | action                 | allow                                |
  | description            |                                      |
  | destination_ip_address | 192.168.2.0/24                       |
  | destination_port       | 22                                   |
  | enabled                | True                                 |
  | firewall_policy_id     |                                      |
  | id                     | f44e6557-7d1b-44f0-a5e6-aad2e77c9ad1 |
  | ip_version             | 4                                    |
  | name                   |                                      |
  | position               |                                      |
  | protocol               | tcp                                  |
  | shared                 | False                                |
  | source_ip_address      | 0.0.0.0/0                            |
  | source_port            | 1234                                 |
  | tenant_id              | e8cf9c9245f24f209263465bcb2cc8c4     |
  +------------------------+--------------------------------------+
  If we want to update this rule, and don't want set source_port or destination_port, we can not done it for now.

  I expect to clear the source_port by using following command:
  [root@node-1 ~]# neutron firewall-rule-update 47cd4350-6c9e-4803-bda7-749774d36dcc --source-port ''
  Updated firewall_rule: 47cd4350-6c9e-4803-bda7-749774d36dcc
  [root@node-1 ~]# neutron firewall-rule-show 47cd4350-6c9e-4803-bda7-749774d36dcc
  +------------------------+--------------------------------------+
  | Field                  | Value                                |
  +------------------------+--------------------------------------+
  | action                 | allow                                |
  | description            |                                      |
  | destination_ip_address | 192.168.2.0/24                       |
  | destination_port       | 22                                   |
  | enabled                | True                                 |
  | firewall_policy_id     |                                      |
  | id                     | 47cd4350-6c9e-4803-bda7-749774d36dcc |
  | ip_version             | 4                                    |
  | name                   |                                      |
  | position               |                                      |
  | protocol               | tcp                                  |
  | shared                 | False                                |
  | source_ip_address      | 0.0.0.0/0                            |
  | source_port            |                                      |
  | tenant_id              | e8cf9c9245f24f209263465bcb2cc8c4     |
  +------------------------+--------------------------------------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1651420/+subscriptions



References