On 11 April 2018 at 11:03, Timothy Redaelli <tredae...@redhat.com> wrote:
> On Wed, 11 Apr 2018 10:05:53 -0700
> Guru Shetty <g...@ovn.org> wrote:
> > On 22 December 2017 at 07:00, Timothy Redaelli <tredae...@redhat.com>
> > wrote:
> > > Since you can't use "ovs-ctl force-reload-kmod" on Fedora/RHEL, due
> > > to systemd dependencies, this commit adds the "force-reload-kmod"
> > > feature on ovs-systemd-reload.
> > >
> > > Signed-off-by: Timothy Redaelli <tredae...@redhat.com>
> > >
> > Tim/Aaron,
> > We have some confusion with this. So, how do we invoke this with
> > systemd? I guess, it is not supposed to be invoked with "service
> > openvswitch reload", right? And why can't we use "ovs-ctl
> > force-reload-kmod" with Fedora/RHEL?
> because on Fedora/RHEL we use systemd dependencies and so we have 3
> (main) service files: openvswitch.spec, ovs-vswitchd.spec and
> ovsdb-server.spec that are interconnected (see rhel/README.RHEL.rst).
> If you use ovs-ctl directly systemd will loose tracks of the new
> ovsdb-server and ovs-vswitchd processes and so you can't restart it by
> using "systemctl restart".
> Moreover it seems ovs-vswitchd is not restarted correctly in this case.
Okay. So, what is the correct way to call force-reload-kmod?
dev mailing list