[Bug 1910209] Re: "systemctl stop openvswitch-switch" will remove /var/run/openvswitch
Yi Yang
1910209 at bugs.launchpad.net
Thu Jan 7 08:05:43 UTC 2021
Christian, thank you so much, the below solution works for me.
$ sudo systemctl edit ovsdb-server.service
[Service]
RuntimeDirectoryPreserve=yes
BTW, only one way to change vhostuser path is using ovs other_config
:vhost-sock-dir, but it is a subdir under /var/run/openvswitch, so it
can't fix this.
https://github.com/openvswitch/ovs/blob/master/lib/dpdk.c#L360.
If you create dpdkvhostuserclient port by yourself and add-port it by
yourself, you can specify full path, but for me, these are handled by
openstack, so I can't control this, other_config:vhost-sock-dir is only
one way to change this, but it is relative path, it can't be beyond
/var/run/openvswitch.
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1910209
Title:
"systemctl stop openvswitch-switch" will remove /var/run/openvswitch
Status in Ubuntu Server Guide:
Fix Released
Status in dpdk package in Ubuntu:
Invalid
Status in openvswitch package in Ubuntu:
Confirmed
Bug description:
TL;DR:
- stoping/restarting OVS clears /var/run/openvswitch
- out of the "vhostuser" connection times a common socket path used
was at /var/run/openvswitch
- if that path used with "vhostuserclient" that removes the sockets
on OVS stop/restart
- Since qemu in server mode only creates this sockets once (as by
the client/server design makes sense) that breaks the guests until
restarted which is what the tech of vhostuserclient wanted to avoid.
+ Workaround: do use a different path like e.g.
"/var/run/vhostuserclient/vhost-user-client-1"
+ Solution: let us think if we could keep the path around on stop/restart
--- vv original report vv ---
My system is Ubuntu 18.04, I installed ovs DPDK by apt-get and used
ovs-vswitchd DPDK version, but when I stop openvswitch-switch (sudo
systemctl stop openvswitch-switch), /var/run/openvswitch is removed,
so the exisitng VMs can't be accessed any more. I don't know why it is
removed and who removed it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/serverguide/+bug/1910209/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list