Bug#878757: [PKG-Openstack-devel] Bug#878757: Openvswitch must started before networking servise

2018-02-08 Thread Thomas Goirand
On 02/04/2018 09:34 PM, Michael Biebl wrote:
> On Mon, 16 Oct 2017 20:28:26 +0700 Fedor Goncharov  wrote:
>> Package: openvswitch-switch
>> Version: 2.6.2~pre+git20161223-3
>> Priority: critical
>>
>> The Openvswitch daemon must be started before the network.service. 
>> Because when the initiation of the network started interfaces from the 
>> options should exist, or if you try to configure openvswitch in 
>> /etc/network/interfaces, then the ovs daemon must be running to execute 
>> commands.
>> Please create a systemd configuration with the option "Before: 
>> networking.service" for a stable version of debian.
> 
> That seems like the wrong thing to do.
> networking.service is specific to ifupdown (auto). We do have several
> other network configuration systems. I hope this was not actually
> applied as a fix? The changelog is unfortunately unclear in that regard:
> 
>   * Added 2 debian/*.service files (Closes: #878757, #771507).
> 
> Thomas, can you please post the complete change that was actually applied.
> 
> 
> Michael

Michael,

Here's the commit:

https://salsa.debian.org/openstack-team/third-party/openvswitch/commit/650fce2f45aac5a46e1cec6ea48dffce0b095c23

I very much would appreciate any comment / suggestion you would make.
Even better if you can send us a patch (or a merge request in Salsa). I
have to admit that the interaction between the .service file and the
ifupdown hook is a bit hard to understand for me, so I took what was in
Ubuntu, and it seemed to work as expected for me.

Cheers,

Thomas Goirand (zigo)



Bug#878757: Openvswitch must started before networking servise

2018-02-04 Thread Michael Biebl
On Mon, 16 Oct 2017 20:28:26 +0700 Fedor Goncharov  wrote:
> Package: openvswitch-switch
> Version: 2.6.2~pre+git20161223-3
> Priority: critical
> 
> The Openvswitch daemon must be started before the network.service. 
> Because when the initiation of the network started interfaces from the 
> options should exist, or if you try to configure openvswitch in 
> /etc/network/interfaces, then the ovs daemon must be running to execute 
> commands.
> Please create a systemd configuration with the option "Before: 
> networking.service" for a stable version of debian.

That seems like the wrong thing to do.
networking.service is specific to ifupdown (auto). We do have several
other network configuration systems. I hope this was not actually
applied as a fix? The changelog is unfortunately unclear in that regard:

  * Added 2 debian/*.service files (Closes: #878757, #771507).

Thomas, can you please post the complete change that was actually applied.


Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#878757: Openvswitch must started before networking servise

2017-10-16 Thread Fedor Goncharov

Package: openvswitch-switch
Version: 2.6.2~pre+git20161223-3
Priority: critical

The Openvswitch daemon must be started before the network.service. 
Because when the initiation of the network started interfaces from the 
options should exist, or if you try to configure openvswitch in 
/etc/network/interfaces, then the ovs daemon must be running to execute 
commands.
Please create a systemd configuration with the option "Before: 
networking.service" for a stable version of debian.