yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #87150
[Bug 1939558] Re: Security group log entry remains in the database after its security group is deleted
Reviewed: https://review.opendev.org/c/openstack/neutron/+/804237
Committed: https://opendev.org/openstack/neutron/commit/7f063223553a18345891bf42e88989edb67038e7
Submitter: "Zuul (22348)"
Branch: master
commit 7f063223553a18345891bf42e88989edb67038e7
Author: Slawek Kaplonski <skaplons@xxxxxxxxxx>
Date: Wed Aug 11 15:22:39 2021 +0200
Delete SG log entries when SG is deleted
When security group is deleted, log entries configured for that SG
weren't removed and stayed in the DB as orphaned entries.
That patch fixes that by subscribe logapi service plugin to the
AFTER_DELETE security group events.
Closes-bug: #1939558
Change-Id: Ibffbbd3b529c31372715d9a064f7cb6bada8c424
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1939558
Title:
Security group log entry remains in the database after its security
group is deleted
Status in neutron:
Fix Released
Bug description:
Issue originally reported by Alex Katz for OSP-16 but I can reproduce
it also in master branch. Original Bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1988793
Description of problem:
After the security group is deleted its corresponding log entry is still presented in the database.
Version-Release number of selected component (if applicable):
How reproducible:
Reproduced in ml2/OVS and ml2/OVN setups
Steps to Reproduce:
# openstack security group create sg_1
# openstack network log create --resource-type security_group --resource sg_1 --event ALL test_log
# openstack security group delete sg_1
# openstack network log show test_log
Actual results:
there is sill entry for `test_log`
Expected results:
security group deletion should fail with the clear error message or the cascade deletion should happen
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1939558/+subscriptions
References