To Reproduce

• Deploy RHOSO with neutron-fwaas driver and log api plugins enabled,
• Create firewall group, policy and some rules and add it to the router's port - see https://docs.openstack.org/neutron/latest/admin/fwaas-v2-scenario.html for more details about how to use fwaas in general,
• Create log for any security group

Expected behavior

• Log resource created as expected

Bug impact

• Please provide information on the impact of this bug to the end user.

Known workaround

• Don't use those 2 service plugins in the same neutron deployment 

Additional context

• I didn't reproduce the issue locally but I've seen it in the CI job scenario: https://sf.apps.int.gpc.ocp-hub.prod.psi.redhat.com/logs/cfc/components-integration/cfc0c91fed684a9284a47e1c525c3510/controller/ci-framework-data/logs/openstack-must-gather/quay-io-openstack-k8s-operators-openstack-must-gather-sha256-455d8661646cfcd53ef4b88a7fd74c6e581492b3abf24b96c0b70cbf0d82f883/namespaces/openstack/pods/neutron-6bcc554b7c-x5kb2/logs/neutron-api.log.gz but I think it should be easily reproducible locally even without tempest tests running