Public bug reported:
The firewall group should be in an INACTIVE state when not associated with a
router and firewall policies, but there may be instances where it is in an
ACTIVE state.
# openstack firewall group show 04bae29d-aad5-4e1d-8685-083a1592a79a
+-------------------+--------------------------------------+
| Field | Value |
+-------------------+--------------------------------------+
| Description | |
| Egress Policy ID | None |
| ID | 04bae29d-aad5-4e1d-8685-083a1592a79a |
| Ingress Policy ID | None |
| Name | ddd2 |
| Ports | [] |
| Project | f16038aec2be4af39242cb8739a29039 |
| Shared | False |
| State | UP |
| Status | ACTIVE |
| project_id | f16038aec2be4af39242cb8739a29039 |
+-------------------+--------------------------------------+
Recurrence process：
1. Create firewall group;
2. Associate with a router;
3. Update the router;
4. Check the firewall status is already ACTIVE;
5. Disassociate from the router, and the firewall status remains ACTIVE.
Version:
OpenStack: Zed
OS: CentOS 9 stream
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2047325
Title:
The firewall group is ACTIVE without associcate with a router or any
firewall policies.
Status in neutron:
New
Bug description:
The firewall group should be in an INACTIVE state when not associated with a
router and firewall policies, but there may be instances where it is in an
ACTIVE state.
# openstack firewall group show 04bae29d-aad5-4e1d-8685-083a1592a79a
+-------------------+--------------------------------------+
| Field | Value |
+-------------------+--------------------------------------+
| Description | |
| Egress Policy ID | None |
| ID | 04bae29d-aad5-4e1d-8685-083a1592a79a |
| Ingress Policy ID | None |
| Name | ddd2 |
| Ports | [] |
| Project | f16038aec2be4af39242cb8739a29039 |
| Shared | False |
| State | UP |
| Status | ACTIVE |
| project_id | f16038aec2be4af39242cb8739a29039 |
+-------------------+--------------------------------------+
Recurrence process：
1. Create firewall group;
2. Associate with a router;
3. Update the router;
4. Check the firewall status is already ACTIVE;
5. Disassociate from the router, and the firewall status remains ACTIVE.
Version:
OpenStack: Zed
OS: CentOS 9 stream
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2047325/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
