Michael, thanks for reporting this. This shouldn't have been missed in the initial patch. I've confirmed that if the config option isn't set at deploy time, openvswitch-switch doesn't get restarted by the charm after rendering /etc/default/openvswitch-switch. The charm needs an update to restart the service in this scenario without doing it every time we run through the hook.
Michael, thanks for reporting this. This shouldn't have been missed in the initial patch. I've confirmed that if the config option isn't set at deploy time, openvswitch-switch doesn't get restarted by the charm after rendering /etc/default/ openvswitch- switch. The charm needs an update to restart the service in this scenario without doing it every time we run through the hook.