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.
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/876716 /opendev. org/openstack/ neutron/ commit/ 63584957203ec9f 5ba165177978213 c3909f81f0
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 63584957203ec9f 5ba165177978213 c3909f81f0
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
Closes-Bug: #2008712