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 Additional info:
verified version - RHOS-17.0-RHEL-9-20220414.n.1 There is an example of all the command output: (overcloud) [stack@undercloud-0 ~]$ openstack security group create sg_1 +-----------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-----------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | created_at | 2022-05-10T07:25:51Z | | description | sg_1 | | id | 845ad072-2752-4a9a-9819-4d6c3127d3e8 | | name | sg_1 | | project_id | f8a8b202c8ec47ff96cb84ad090642d2 | | revision_number | 1 | | rules | created_at='2022-05-10T07:25:51Z', direction='egress', ethertype='IPv4', id='686e2822-5cd0-45d9-89ff-972f2cac95d1', standard_attr_id='21668', updated_at='2022-05-10T07:25:51Z' | | | created_at='2022-05-10T07:25:51Z', direction='egress', ethertype='IPv6', id='b913d2c3-052e-436d-8765-8980bfc8f0c3', standard_attr_id='21671', updated_at='2022-05-10T07:25:51Z' | | stateful | None | | tags | [] | | updated_at | 2022-05-10T07:25:51Z | +-----------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ (overcloud) [stack@undercloud-0 ~]$ openstack network log create --resource-type security_group --resource sg_1 --event ALL test_log +-----------------+--------------------------------------+ | Field | Value | +-----------------+--------------------------------------+ | Description | | | Enabled | True | | Event | ALL | | ID | 6234ed42-9a20-4926-8e71-978282d7bebc | | Name | test_log | | Project | f8a8b202c8ec47ff96cb84ad090642d2 | | Resource | 845ad072-2752-4a9a-9819-4d6c3127d3e8 | | Target | None | | Type | security_group | | created_at | 2022-05-10T07:26:08Z | | revision_number | 0 | | tenant_id | f8a8b202c8ec47ff96cb84ad090642d2 | | updated_at | 2022-05-10T07:26:08Z | +-----------------+--------------------------------------+ (overcloud) [stack@undercloud-0 ~]$ openstack network log list +--------------------------------------+---------+----------+----------------+---------------------------------------------------------------+ | ID | Enabled | Name | Type | Summary | +--------------------------------------+---------+----------+----------------+---------------------------------------------------------------+ | 6234ed42-9a20-4926-8e71-978282d7bebc | True | test_log | security_group | Event: ALL, | | | | | | Logged: (security_group) 845ad072-2752-4a9a-9819-4d6c3127d3e8 | +--------------------------------------+---------+----------+----------------+---------------------------------------------------------------+ (overcloud) [stack@undercloud-0 ~]$ openstack security group delete sg_1 (overcloud) [stack@undercloud-0 ~]$ openstack network log list (overcloud) [stack@undercloud-0 ~]$ openstack network log show test_log Unable to find log with name or id 'test_log'
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2022:6543