Wrong ordered fw_rules when set them into fw_policy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Low
|
zhaobo |
Bug Description
There are 3 sample fw_rules in server. And I expect the order is tcp - ping - denyany
openstack firewall group rule list
+------
| ID | Name | Enabled | Summary |
+------
| 563841d1-
| | | | source(port): none specified(none specified), |
| | | | dest(port): none specified(none specified), |
| | | | deny |
| ab93b257-
| | | | source(port): 1.1.1.1(none specified), |
| | | | dest(port): none specified(none specified), |
| | | | reject |
| d53d4015-
| | | | source(port): 2.2.2.2(2222), |
| | | | dest(port): none specified(none specified), |
| | | | deny |
+------
Then I set them into fw_policy as my expect order.
openstack firewall group policy set test --firewall-rule tcp
openstack firewall group policy set test --firewall-rule ping
openstack firewall group policy set test --firewall-rule denyany
But I saw the order had changed and the backend driver will apply the rules in the wrong order.
openstack firewall group policy list
+------
| ID | Name | Firewall Rules |
+------
| 1b93f923-
+------
Currently, neutron-fwaas accept the arguments with full list of fw_rules on fw_policy create/update. So this must be a OSC bug.
Hi zhaobo: The data is coming as an ordered list. I do not think this is an issue with OSC, will look into from the FWaaS side as well.