Comment 4 for bug 1978497

Currently, the master code does not allow one port to be associated with multiple firewall groups, call chain is
update_firewall_group[1] -> update_firewall_group[2] -> _set_ports_for_firewall_group[3] -> raise FirewallGroupPortInUse[4].
The current database design also allows only one associated record per port[5][6]

Which version of the test is this？

[1] https://opendev.org/openstack/neutron-fwaas/src/branch/master/neutron_fwaas/services/firewall/fwaas_plugin_v2.py#L359
[2] https://opendev.org/openstack/neutron-fwaas/src/branch/master/neutron_fwaas/db/firewall/v2/firewall_db_v2.py#L985
[3] https://opendev.org/openstack/neutron-fwaas/src/branch/master/neutron_fwaas/db/firewall/v2/firewall_db_v2.py#L822
[4] https://opendev.org/openstack/neutron-fwaas/src/branch/master/neutron_fwaas/db/firewall/v2/firewall_db_v2.py#L838
[5] https://opendev.org/openstack/neutron-fwaas/src/branch/master/neutron_fwaas/db/migration/alembic_migrations/versions/queens/expand/f24e0d5e5bff_uniq_firewallgroupportassociation0port.py
[6] https://review.opendev.org/c/openstack/neutron-fwaas/+/512154