Comment 2 for bug 1772881

After some debug time I found that there is no easy and reliable way to fix this bug. Upstream configuration file for openvswitch-switch service was written in an odd way: there is defined only pre-start and post-stop scripts which contains daemon start/stop logic. There is no "script"/"exec" section. Without it upstart does not know "what should I monitor" (this is also the reason of false-positive "service status" command) and "respawn" feature will not works even if we add it. Proper solution requires rewriting more than half of upstart configuration file which is risky enough.

Also we were notified that there is no cases of openvswitch daemon's failures - the observed one was a result of consequence of actions during testing. This means that this bug is out of scope of maintenance updates because fix for it is too risky and can produce more errors than fixing this one.