[ovs-discuss] systemd ovs-vswitchd starts too early
benoitne at gmail.com
Sat Feb 6 13:14:54 UTC 2016
On Archlinux (or Parabola) there is only one systemd unit provied (no
Description = Open vSwitch Daemon
Documentation = man:ovs-vswitchd
Wants = network.target
Before = network.target
Requires = ovsdb-server.service
After = ovsdb-server.service
ExecStartPre = /sbin/modprobe openvswitch
PIDFile = /run/openvswitch/ovs-vswitchd.pid
ExecStart = /usr/sbin/ovs-vswitchd
WantedBy = multi-user.target
I have the same issue than Mark, no way for openvswitch to start
correctly, I have tested multiple scenarios
On 02/04/16 23:29, Flavio Leitner wrote:
> On Thu, 4 Feb 2016 22:10:32 +0000
> Benoit <benoitne at gmail.com> wrote:
>> Apparently no,
>> What are the rhel/Fedora scripts just for me to double check?
> The issue that the interfaces show up before their initialization is
> independent of the OS. It happens when OVS is started because the
> configuration survives between reboots.
>> On 04/02/16 20:39, Flavio Leitner wrote:
>>> On Thu, 4 Feb 2016 17:23:44 +0000
>>> Benoit <benoitne at gmail.com> wrote:
>>>> Just to say that I got the same issue on ArchLinux (Parabola to be
>>>> accurate) which use SystemD as well.
>>>> I wrote something probably one month ago here but not a lot of
>>> Does ArchLinux use rhel/Fedora systemd initialization scripts?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the discuss