The firewall group's status is active when firewall group has no any policy

Bug #1872439 reported by yuanshuo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
New
Undecided
Unassigned

Bug Description

Creating a firewall group with policies and 1 interface ports.
[root@test25g04 yuanshuo1]# openstack firewall group show ys-normal-fw1 +-------------------+-------------------------------------------+
| Field | Value |
+-------------------+-------------------------------------------+
| Description | |
| Egress Policy ID | 0910e062-f961-45aa-928a-03cdc8725da9 |
| ID | f3b8441a-dcdb-457d-90bc-71571bffa155 |
| Ingress Policy ID | 9873dfd4-f235-463e-a246-67217ecdbdb0 |
| Name | ys-normal-fw1 |
| Ports | [u'ef283f14-ed0b-4dbb-bde4-2e08b66e73fc'] |
| Project | 17bf57ec04994db2b591fda36c368e99 |
| Shared | False |
| State | UP |
| Status | ACTIVE |
| project_id | 17bf57ec04994db2b591fda36c368e99 |
| revision_number | 9 |
| tags | [] |
+-------------------+-------------------------------------------+

Then update the firewall group, but the status of firewall group is active.
[root@test25g04 yuanshuo1]# openstack firewall group set --no-ingress-firewall-policy --no-egress-firewall-policy ys-normal-fw1
[root@test25g04 yuanshuo1]# openstack firewall group show ys-normal-fw1
+-------------------+-------------------------------------------+
| Field | Value |
+-------------------+-------------------------------------------+
| Description | |
| Egress Policy ID | None |
| ID | f3b8441a-dcdb-457d-90bc-71571bffa155 |
| Ingress Policy ID | None |
| Name | ys-normal-fw1 |
| Ports | [u'ef283f14-ed0b-4dbb-bde4-2e08b66e73fc'] |
| Project | 17bf57ec04994db2b591fda36c368e99 |
| Shared | False |
| State | UP |
| Status | ACTIVE |
| project_id | 17bf57ec04994db2b591fda36c368e99 |
| revision_number | 10 |
| tags | [] |
+-------------------+-------------------------------------------+

Tags: fwaas
tags: added: fwaas
Revision history for this message
Ryan Tidwell (ryan-tidwell) wrote :

What version are you observing this behavior with? I would defer to someone with more FWaaS expertise, but this seems like expected behavior. I don't see why this sequence of commands would lead the status of the firewall group to be anything other than ACTIVE. I wouldn't expect the status field to indicate whether it is bound to policies or not, I would simply expect status to indicate proper provisioning of the resource.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.