Based on bug #2008712 if we have a security-group which
is the remote group of a 2nd security-group, the backend
never deletes the rule of the 2nd group which
remote_group_id is the original security-group.
By AFTER_DELETE event for each rule that has the
security_group_id as remote_group_id, we can make the
mech drivers do their work and delete these rules in the
backend.
Change-Id: I207ecf7954b06507e03cb16b502ceb6e2807e0e7
(cherry picked from commit 63584957203ec9f5ba165177978213c3909f81f0)
Closes-Bug: #2008712
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/881661 /opendev. org/openstack/ neutron/ commit/ a15eece7712d94c ec7a6de6472b46a 1e81139dbc
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2023.1
commit a15eece7712d94c ec7a6de6472b46a 1e81139dbc
Author: elajkat <email address hidden>
Date: Fri Mar 10 13:29:48 2023 +0100
Delete sg rule which remote is the deleted sg
Based on bug #2008712 if we have a security-group which group_id as remote_group_id, we can make the
is the remote group of a 2nd security-group, the backend
never deletes the rule of the 2nd group which
remote_group_id is the original security-group.
By AFTER_DELETE event for each rule that has the
security_
mech drivers do their work and delete these rules in the
backend.
Change-Id: I207ecf7954b065 07e03cb16b502ce b6e2807e0e7 5ba165177978213 c3909f81f0)
(cherry picked from commit 63584957203ec9f
Closes-Bug: #2008712