© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
9199653
demo site
(Get the code!)
openvswitch-switch consists of three services actually:
openvswitch-
-> ovsdb-server.
-> ovs-vswitchd.
Of those the start/stop/restart of ovsdb-server.
The path is created due to /lib/systemd/
RuntimeDirector
RuntimeDirector
Acoording to [1] that will be "In case of RuntimeDirectory= the innermost subdirectories are removed when the unit is stopped. It is possible to preserve the specified directories in this case if RuntimeDirector
So the behavior atm is exactly as configured.
The service files are "ours" (= packaging). Upstream only has rhel service files and those do not dynamically add/remove the path. Instead I've even seen discussions [2] saying about RuntimeDirector
We can add a change via:
$ sudo systemctl edit ovsdb-server.
[Service]
RuntimeDirector
That will keep the directory alive and avoid the issue.
@Yi - for now that could be your solution as it would avoid having you to reconfigure (potentially many) other places.
Packaging wise that would be as easy as [3]
But I'm unsure if there is intention in removing this directory - e.g. to get the DB state cleaned and re-initialized for sure. I'd leave that up to James/Frode who have looked more at OVS. Based on their decision we can try to make this statement part of the default config (or not).
Subscribing James/Frode here on the bug and on the MP to carry on from here.
[1]: https:/
[2]: https:/
[3]: https:/