| 2020-02-13 12:11:19 |
Frode Nordahl |
bug |
|
|
added bug |
| 2020-02-13 12:11:26 |
Frode Nordahl |
charm-ovn-central: status |
New |
Triaged |
|
| 2020-02-13 12:11:29 |
Frode Nordahl |
charm-ovn-central: importance |
Undecided |
Critical |
|
| 2020-02-13 12:11:32 |
Frode Nordahl |
charm-ovn-central: assignee |
|
Frode Nordahl (fnordahl) |
|
| 2020-02-13 12:11:36 |
Frode Nordahl |
charm-ovn-central: milestone |
|
20.02 |
|
| 2020-02-13 15:43:33 |
Frode Nordahl |
description |
The intention of the ``OVNCentralCharm.configure_firewall`` method was to update the existing rules in an additive manner for new entries and removal of no longer existing entries.
The reality is that each call to the method will remove all firewall rules and re-instate them, with the obvious undesired side effect of active connections being interrupted. |
The intention of the ``OVNCentralCharm.configure_firewall`` method was to update the existing rules in an additive manner for new entries and removal of no longer existing entries.
The reality is that each call to the method will remove all firewall rules and re-instate them, with the obvious undesired side effect of active connections being interrupted.
The calls to `charmhelpers.contrib.network.default_policy` appear to be the culprits, and I think we need to move these and make sure they are called once at initial deploy. |
|
| 2020-02-14 07:20:21 |
OpenStack Infra |
charm-ovn-central: status |
Triaged |
In Progress |
|
| 2020-02-14 13:41:37 |
OpenStack Infra |
charm-ovn-central: status |
In Progress |
Fix Committed |
|
| 2020-02-17 17:26:05 |
Liam Young |
charm-ovn-central: status |
Fix Committed |
Fix Released |
|
