dded354a5f
If an existing firewall rule already associated with a firewall policy is associated with a different firewall policy, the new association should fail. The check for the existing association was not being made, hence the firewall rule was being removed from the older policy and being associated with the newer policy (incorrect behavior). This is being fixed here. If the association with the newer policy has to be made the rule should first be removed from the existing policy association. Change-Id: I30c41d77e7fde673f0dccbc98e1cd7bd0d7b384f Closes-Bug: #1223465 |
||
---|---|---|
.. | ||
__init__.py | ||
firewall_db.py |