Bug#771863: Service does not start or parse interfaces correctly

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#771863: Service does not start or parse interfaces correctly

Fabio Fantoni-2
One maintainer or debian developer can do a new build of ovs with the fix available in 2.3.1 please?

  • Version 2.3.0+git20140819-2 of openvswitch is marked for autoremoval from testing on 2015-01-15.
  • It is affected by RC bug #771863.

Without this fix openvswitch will be removed from Jessie and I think this would be a bad thing.

Thanks for any reply and sorry for my bad english.

Reply | Threaded
Open this post in threaded view
|

Bug#771863: [ovs-dev] Bug#771863: Service does not start or parse interfaces correctly

Joe Stringer
On 18 December 2014 at 01:00, Fabio Fantoni <[hidden email]> wrote:

> One maintainer or debian developer can do a new build of ovs with the fix
> available in 2.3.1 please?
>
>>   * Version 2.3.0+git20140819-2 of openvswitch is marked for
>>     autoremoval from testing on 2015-01-15.
>>   * It is affected by RC bug #771863 <https://bugs.debian.org/771863>.
>>
>
> Without this fix openvswitch will be removed from Jessie and I think this
> would be a bad thing.
>
> Thanks for any reply and sorry for my bad english.

Ben usually takes care of this sort of thing, but he is out on holiday
through to Christmas.

Simon, would you be able to take care of this?


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#771863: [ovs-dev] Bug#771863: Service does not start or parse interfaces correctly

Simon Horman
On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:

> On 18 December 2014 at 01:00, Fabio Fantoni <[hidden email]> wrote:
> > One maintainer or debian developer can do a new build of ovs with the fix
> > available in 2.3.1 please?
> >
> >>   * Version 2.3.0+git20140819-2 of openvswitch is marked for
> >>     autoremoval from testing on 2015-01-15.
> >>   * It is affected by RC bug #771863 <https://bugs.debian.org/771863>.
> >>
> >
> > Without this fix openvswitch will be removed from Jessie and I think this
> > would be a bad thing.
> >
> > Thanks for any reply and sorry for my bad english.
>
> Ben usually takes care of this sort of thing, but he is out on holiday
> through to Christmas.
>
> Simon, would you be able to take care of this?

Sure, I have uploaded a fresh package which attempts to do so.
It contains no other changes.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#771863: [PKG-Openstack-devel] [ovs-dev] Bug#771863: Service does not start or parse interfaces correctly

Thomas Goirand-3
On 12/19/2014 11:50 AM, Simon Horman wrote:

> On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
>> On 18 December 2014 at 01:00, Fabio Fantoni <[hidden email]> wrote:
>>> One maintainer or debian developer can do a new build of ovs with the fix
>>> available in 2.3.1 please?
>>>
>>>>   * Version 2.3.0+git20140819-2 of openvswitch is marked for
>>>>     autoremoval from testing on 2015-01-15.
>>>>   * It is affected by RC bug #771863 <https://bugs.debian.org/771863>.
>>>>
>>>
>>> Without this fix openvswitch will be removed from Jessie and I think this
>>> would be a bad thing.
>>>
>>> Thanks for any reply and sorry for my bad english.
>>
>> Ben usually takes care of this sort of thing, but he is out on holiday
>> through to Christmas.
>>
>> Simon, would you be able to take care of this?
>
> Sure, I have uploaded a fresh package which attempts to do so.
> It contains no other changes.

Simon,

Did you ask for an unblock to the release team?

Cheers,

Thomas Goirand (zigo)


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#771863: [ovs-dev] Bug#771863: [PKG-Openstack-devel] Bug#771863: Service does not start or parse interfaces correctly

Simon Horman
On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:

> On 12/19/2014 11:50 AM, Simon Horman wrote:
> > On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
> >> On 18 December 2014 at 01:00, Fabio Fantoni <[hidden email]> wrote:
> >>> One maintainer or debian developer can do a new build of ovs with the fix
> >>> available in 2.3.1 please?
> >>>
> >>>>   * Version 2.3.0+git20140819-2 of openvswitch is marked for
> >>>>     autoremoval from testing on 2015-01-15.
> >>>>   * It is affected by RC bug #771863 <https://bugs.debian.org/771863>.
> >>>>
> >>>
> >>> Without this fix openvswitch will be removed from Jessie and I think this
> >>> would be a bad thing.
> >>>
> >>> Thanks for any reply and sorry for my bad english.
> >>
> >> Ben usually takes care of this sort of thing, but he is out on holiday
> >> through to Christmas.
> >>
> >> Simon, would you be able to take care of this?
> >
> > Sure, I have uploaded a fresh package which attempts to do so.
> > It contains no other changes.
>
> Simon,
>
> Did you ask for an unblock to the release team?

Hi Thomas,

I would be grateful for some assistance understanding what needs to
be done there. At this point I have not made any unblock requests.
But the intention of this upload was to provide something to
be included in Jessie and thus it needs to migrate to testing somehow.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#771863: [ovs-dev] Bug#771863: [PKG-Openstack-devel] Bug#771863: Service does not start or parse interfaces correctly

Fabio Fantoni-2
Il 19/12/2014 15:25, Simon Horman ha scritto:

> On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
>> On 12/19/2014 11:50 AM, Simon Horman wrote:
>>> On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
>>>> On 18 December 2014 at 01:00, Fabio Fantoni <[hidden email]> wrote:
>>>>> One maintainer or debian developer can do a new build of ovs with the fix
>>>>> available in 2.3.1 please?
>>>>>
>>>>>>    * Version 2.3.0+git20140819-2 of openvswitch is marked for
>>>>>>      autoremoval from testing on 2015-01-15.
>>>>>>    * It is affected by RC bug #771863 <https://bugs.debian.org/771863>.
>>>>>>
>>>>> Without this fix openvswitch will be removed from Jessie and I think this
>>>>> would be a bad thing.
>>>>>
>>>>> Thanks for any reply and sorry for my bad english.
>>>> Ben usually takes care of this sort of thing, but he is out on holiday
>>>> through to Christmas.
>>>>
>>>> Simon, would you be able to take care of this?
>>> Sure, I have uploaded a fresh package which attempts to do so.
>>> It contains no other changes.
>> Simon,
>>
>> Did you ask for an unblock to the release team?
> Hi Thomas,
>
> I would be grateful for some assistance understanding what needs to
> be done there. At this point I have not made any unblock requests.
> But the intention of this upload was to provide something to
> be included in Jessie and thus it needs to migrate to testing somehow.
Thanks for the upload.
These information I think should be useful:
https://release.debian.org/jessie/freeze_policy.html
And here an example of unblock request:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771931


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#771863: [PKG-Openstack-devel] [ovs-dev] Bug#771863: Bug#771863: Service does not start or parse interfaces correctly

Thomas Goirand-3
In reply to this post by Simon Horman
On 12/19/2014 10:25 PM, Simon Horman wrote:

> On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
>> On 12/19/2014 11:50 AM, Simon Horman wrote:
>>> On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
>>>> On 18 December 2014 at 01:00, Fabio Fantoni <[hidden email]> wrote:
>>>>> One maintainer or debian developer can do a new build of ovs with the fix
>>>>> available in 2.3.1 please?
>>>>>
>>>>>>   * Version 2.3.0+git20140819-2 of openvswitch is marked for
>>>>>>     autoremoval from testing on 2015-01-15.
>>>>>>   * It is affected by RC bug #771863 <https://bugs.debian.org/771863>.
>>>>>>
>>>>>
>>>>> Without this fix openvswitch will be removed from Jessie and I think this
>>>>> would be a bad thing.
>>>>>
>>>>> Thanks for any reply and sorry for my bad english.
>>>>
>>>> Ben usually takes care of this sort of thing, but he is out on holiday
>>>> through to Christmas.
>>>>
>>>> Simon, would you be able to take care of this?
>>>
>>> Sure, I have uploaded a fresh package which attempts to do so.
>>> It contains no other changes.
>>
>> Simon,
>>
>> Did you ask for an unblock to the release team?
>
> Hi Thomas,
>
> I would be grateful for some assistance understanding what needs to
> be done there. At this point I have not made any unblock requests.
> But the intention of this upload was to provide something to
> be included in Jessie and thus it needs to migrate to testing somehow.

I'm sending the unblock request as we speak.

Thomas


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#771863: [PKG-Openstack-devel] [ovs-dev] Bug#771863: Bug#771863: Service does not start or parse interfaces correctly

Thomas Goirand-3
On 12/19/2014 11:32 PM, Thomas Goirand wrote:

> On 12/19/2014 10:25 PM, Simon Horman wrote:
>> On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
>>> On 12/19/2014 11:50 AM, Simon Horman wrote:
>>>> On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
>>>>> On 18 December 2014 at 01:00, Fabio Fantoni <[hidden email]> wrote:
>>>>>> One maintainer or debian developer can do a new build of ovs with the fix
>>>>>> available in 2.3.1 please?
>>>>>>
>>>>>>>   * Version 2.3.0+git20140819-2 of openvswitch is marked for
>>>>>>>     autoremoval from testing on 2015-01-15.
>>>>>>>   * It is affected by RC bug #771863 <https://bugs.debian.org/771863>.
>>>>>>>
>>>>>>
>>>>>> Without this fix openvswitch will be removed from Jessie and I think this
>>>>>> would be a bad thing.
>>>>>>
>>>>>> Thanks for any reply and sorry for my bad english.
>>>>>
>>>>> Ben usually takes care of this sort of thing, but he is out on holiday
>>>>> through to Christmas.
>>>>>
>>>>> Simon, would you be able to take care of this?
>>>>
>>>> Sure, I have uploaded a fresh package which attempts to do so.
>>>> It contains no other changes.
>>>
>>> Simon,
>>>
>>> Did you ask for an unblock to the release team?
>>
>> Hi Thomas,
>>
>> I would be grateful for some assistance understanding what needs to
>> be done there. At this point I have not made any unblock requests.
>> But the intention of this upload was to provide something to
>> be included in Jessie and thus it needs to migrate to testing somehow.
>
> I'm sending the unblock request as we speak.
>
> Thomas

https://bugs.debian.org/773534

Thomas


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#771863: [PKG-Openstack-devel] [ovs-dev] Bug#771863: Bug#771863: Service does not start or parse interfaces correctly

Simon Horman
On Fri, Dec 19, 2014 at 11:43:42PM +0800, Thomas Goirand wrote:

> On 12/19/2014 11:32 PM, Thomas Goirand wrote:
> > On 12/19/2014 10:25 PM, Simon Horman wrote:
> >> On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
> >>> On 12/19/2014 11:50 AM, Simon Horman wrote:
> >>>> On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
> >>>>> On 18 December 2014 at 01:00, Fabio Fantoni <[hidden email]> wrote:
> >>>>>> One maintainer or debian developer can do a new build of ovs with the fix
> >>>>>> available in 2.3.1 please?
> >>>>>>
> >>>>>>>   * Version 2.3.0+git20140819-2 of openvswitch is marked for
> >>>>>>>     autoremoval from testing on 2015-01-15.
> >>>>>>>   * It is affected by RC bug #771863 <https://bugs.debian.org/771863>.
> >>>>>>>
> >>>>>>
> >>>>>> Without this fix openvswitch will be removed from Jessie and I think this
> >>>>>> would be a bad thing.
> >>>>>>
> >>>>>> Thanks for any reply and sorry for my bad english.
> >>>>>
> >>>>> Ben usually takes care of this sort of thing, but he is out on holiday
> >>>>> through to Christmas.
> >>>>>
> >>>>> Simon, would you be able to take care of this?
> >>>>
> >>>> Sure, I have uploaded a fresh package which attempts to do so.
> >>>> It contains no other changes.
> >>>
> >>> Simon,
> >>>
> >>> Did you ask for an unblock to the release team?
> >>
> >> Hi Thomas,
> >>
> >> I would be grateful for some assistance understanding what needs to
> >> be done there. At this point I have not made any unblock requests.
> >> But the intention of this upload was to provide something to
> >> be included in Jessie and thus it needs to migrate to testing somehow.
> >
> > I'm sending the unblock request as we speak.
> >
> > Thomas
>
> https://bugs.debian.org/773534

Thanks.

I sent one too, following Fabio Fantoni's excellent advice. I suppose the
two bugs can be merged if/when mine shows up in the bug tracker.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#771863: [PKG-Openstack-devel] [ovs-dev] Bug#771863: Bug#771863: Service does not start or parse interfaces correctly

Fabio Fantoni-2
Il 19/12/2014 17:04, Simon Horman ha scritto:

> On Fri, Dec 19, 2014 at 11:43:42PM +0800, Thomas Goirand wrote:
>> On 12/19/2014 11:32 PM, Thomas Goirand wrote:
>>> On 12/19/2014 10:25 PM, Simon Horman wrote:
>>>> On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
>>>>> On 12/19/2014 11:50 AM, Simon Horman wrote:
>>>>>> On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
>>>>>>> On 18 December 2014 at 01:00, Fabio Fantoni <[hidden email]> wrote:
>>>>>>>> One maintainer or debian developer can do a new build of ovs with the fix
>>>>>>>> available in 2.3.1 please?
>>>>>>>>
>>>>>>>>>    * Version 2.3.0+git20140819-2 of openvswitch is marked for
>>>>>>>>>      autoremoval from testing on 2015-01-15.
>>>>>>>>>    * It is affected by RC bug #771863 <https://bugs.debian.org/771863>.
>>>>>>>>>
>>>>>>>> Without this fix openvswitch will be removed from Jessie and I think this
>>>>>>>> would be a bad thing.
>>>>>>>>
>>>>>>>> Thanks for any reply and sorry for my bad english.
>>>>>>> Ben usually takes care of this sort of thing, but he is out on holiday
>>>>>>> through to Christmas.
>>>>>>>
>>>>>>> Simon, would you be able to take care of this?
>>>>>> Sure, I have uploaded a fresh package which attempts to do so.
>>>>>> It contains no other changes.
>>>>> Simon,
>>>>>
>>>>> Did you ask for an unblock to the release team?
>>>> Hi Thomas,
>>>>
>>>> I would be grateful for some assistance understanding what needs to
>>>> be done there. At this point I have not made any unblock requests.
>>>> But the intention of this upload was to provide something to
>>>> be included in Jessie and thus it needs to migrate to testing somehow.
>>> I'm sending the unblock request as we speak.
>>>
>>> Thomas
>> https://bugs.debian.org/773534
> Thanks.
>
> I sent one too, following Fabio Fantoni's excellent advice. I suppose the
> two bugs can be merged if/when mine shows up in the bug tracker.

I tried 2.3.0+git20140819-3 building it in wheezy with kernel 3.16 from
backports but bridge of my test was still not working:

> auto xenbr0
> allow-ovs xenbr0
> iface xenbr0 inet static
>        address 192.168.1.90
>         netmask 255.255.255.0
>         network 192.168.1.0
>         broadcast 192.168.1.255
>         gateway 192.168.1.200
>         ovs_type OVSBridge
>         ovs_ports eth0
>
> auto eth0
> allow-xenbr0 eth0
> iface eth0 inet manual
>         ovs_bridge xenbr0
>         ovs_type OVSPort
>
> auto xenbr1
> allow-ovs xenbr1
> iface xenbr1 inet static
>        address 192.168.45.91
>         netmask 255.255.255.0
>         network 192.168.45.0
>         broadcast 192.168.45.255
>         ovs_type OVSBridge
>         ovs_ports vlan100
>
> allow-xenbr1 vlan100
> iface vlan100 inet manual
>         ovs_bridge xenbr1
>         ovs_type OVSIntPort
>         ovs_options tag=100
>         ovs_extra set interface ${IFACE}
> external-ids:iface-id=$(hostname -s)

For have it working I had to do "service networking restart".
I found probably final solution applying also this patch:
http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=9a8b5cc1a3d941c0e33f3f5b5ac260a35a8130af
Even if seems not good in some cases.
I don't know if also Jessie have this problem but probably yes. If yes I
think this bug is only partially solves with 2.3.0+git20140819-3.



I had also another start problem probably not related to this, after
some hours xenbr0 stopped to working.
I not found any useful errors about in logs, only some strange thing, in
ifconfig xenbr0 was without the static ip, in syslog keep tried to
acquire configuration with dhcp failing (dhcp server present and working
in lan).
After "service networking restart" was working again but I not
understand was happen and why :(
Someone have any idea about?



Thanks for any reply and sorry for my bad english.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#771863: [ovs-dev] Bug#771863: [PKG-Openstack-devel] Bug#771863: Bug#771863: Service does not start or parse interfaces correctly

Gurucharan Shetty
>
> I tried 2.3.0+git20140819-3 building it in wheezy with kernel 3.16 from
> backports but bridge of my test was still not working:
>>
>> auto xenbr0
>> allow-ovs xenbr0
>> iface xenbr0 inet static
>>        address 192.168.1.90
>>         netmask 255.255.255.0
>>         network 192.168.1.0
>>         broadcast 192.168.1.255
>>         gateway 192.168.1.200
>>         ovs_type OVSBridge
>>         ovs_ports eth0
>>
>> auto eth0
You should not be using 'auto' above. eth0 is a port of an OVS bridge
and it should be configured after 'xenbr0' is configured.

>> allow-xenbr0 eth0
>> iface eth0 inet manual
>>         ovs_bridge xenbr0
>>         ovs_type OVSPort
>>
>> auto xenbr1
>> allow-ovs xenbr1
>> iface xenbr1 inet static
>>        address 192.168.45.91
>>         netmask 255.255.255.0
>>         network 192.168.45.0
>>         broadcast 192.168.45.255
>>         ovs_type OVSBridge
>>         ovs_ports vlan100
>>
>> allow-xenbr1 vlan100
>> iface vlan100 inet manual
>>         ovs_bridge xenbr1
>>         ovs_type OVSIntPort
>>         ovs_options tag=100
>>         ovs_extra set interface ${IFACE} external-ids:iface-id=$(hostname
>> -s)
Without applying the below mentioned patch, does your problem go away
if you remove all the 'auto' for xenbr0 and xenbr1 also?
>
>
> For have it working I had to do "service networking restart".
> I found probably final solution applying also this patch:
> http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=9a8b5cc1a3d941c0e33f3f5b5ac260a35a8130af
The above patch adds the ability to configure OVS with 'auto'
configured and additionally has the following information:
"""
Notes on dependencies:
---------------------

openvswitch-switch depends on $network, $named $remote_fs and $syslog to start.
This creates some startup dependency issues.

* Since openvswitch utilities are placed in /usr and /usr can be mounted
through NFS, openvswitch has to start after it.  But if a user uses openvswitch
for all his networking needs and hence to mount NFS, there will be a deadlock.
So, if /usr is mounted through NFS and openvswitch is used for all networking,
the administrator should figure out a way to mount NFS before starting OVS.
One way to do this is in initramfs.

* Since openvswitch starts after $network, $remote_fs and $syslog, any startup
script that depends on openvswitch but starts before it, needs to be changed
to depend on openvswitch-switch too.

* Ideally, an admin should not add openvswitch bridges in the 'auto'
section of the 'interfaces' file.  This is because, when ifupdown starts
working on bridges listed in 'auto', openvswitch has not yet started.

But, if the admin wants to go down this route and adds openvswitch bridges
in the 'auto' section, openvswitch-switch will forcefully be started when
ifupdown kicks in. In a case like this, the admin needs to make sure that /usr
has already been mounted and that a remote $syslog (if used) is ready to
receive openvswitch logs.
"""


> Even if seems not good in some cases.
Does the above explanation give any hints on why it wouldn't work in some cases?

> I don't know if also Jessie have this problem but probably yes. If yes I
> think this bug is only partially solves with 2.3.0+git20140819-3.
>
>
>
> I had also another start problem probably not related to this, after some
> hours xenbr0 stopped to working.
> I not found any useful errors about in logs, only some strange thing, in
> ifconfig xenbr0 was without the static ip, in syslog keep tried to acquire
> configuration with dhcp failing (dhcp server present and working in lan).
> After "service networking restart" was working again but I not understand
> was happen and why :(
> Someone have any idea about?
>
>
>
> Thanks for any reply and sorry for my bad english.
> _______________________________________________
> dev mailing list
> [hidden email]
> http://openvswitch.org/mailman/listinfo/dev


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#771863: [PKG-Openstack-devel] [ovs-dev] Bug#771863: Bug#771863: Service does not start or parse interfaces correctly

Joe Stringer
In reply to this post by Fabio Fantoni-2
On 23 December 2014 at 03:12, Fabio Fantoni <[hidden email]> wrote:
> For have it working I had to do "service networking restart".
> I found probably final solution applying also this patch:
> http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=9a8b5cc1a3d941c0e33f3f5b5ac260a35a8130af
> Even if seems not good in some cases.
> I don't know if also Jessie have this problem but probably yes. If yes I
> think this bug is only partially solves with 2.3.0+git20140819-3.

FYI, the above URL points to an outdated git and may go away; OVS has
migrated to GitHub:
https://github.com/openvswitch/ovs/commit/9a8b5cc1a3d941c0e33f3f5b5ac260a35a8130af

If you accessed the above URL via the OVS website somehow, please get
in touch with me off-list so we can fix the links to point to the
correct location.


> I had also another start problem probably not related to this, after some
> hours xenbr0 stopped to working.
> I not found any useful errors about in logs, only some strange thing, in
> ifconfig xenbr0 was without the static ip, in syslog keep tried to acquire
> configuration with dhcp failing (dhcp server present and working in lan).
> After "service networking restart" was working again but I not understand
> was happen and why :(
> Someone have any idea about?

I see that Guru has suggested a possible fix; if that does not address
your issue, you could send your question to [hidden email] or
open a fresh debian bug (or both!). It would be helpful to provide
related logs (ovs-vswitchd.log and/or syslog), OVS versions and OVS
configuration.

Thanks,
Joe


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#771863: [ovs-dev] Bug#771863: [PKG-Openstack-devel] Bug#771863: Bug#771863: Service does not start or parse interfaces correctly

Fabio Fantoni-2
In reply to this post by Gurucharan Shetty
Il 23/12/2014 16:27, Gurucharan Shetty ha scritto:

>> I tried 2.3.0+git20140819-3 building it in wheezy with kernel 3.16 from
>> backports but bridge of my test was still not working:
>>> auto xenbr0
>>> allow-ovs xenbr0
>>> iface xenbr0 inet static
>>>         address 192.168.1.90
>>>          netmask 255.255.255.0
>>>          network 192.168.1.0
>>>          broadcast 192.168.1.255
>>>          gateway 192.168.1.200
>>>          ovs_type OVSBridge
>>>          ovs_ports eth0
>>>
>>> auto eth0
> You should not be using 'auto' above. eth0 is a port of an OVS bridge
> and it should be configured after 'xenbr0' is configured.
>
>>> allow-xenbr0 eth0
>>> iface eth0 inet manual
>>>          ovs_bridge xenbr0
>>>          ovs_type OVSPort
>>>
>>> auto xenbr1
>>> allow-ovs xenbr1
>>> iface xenbr1 inet static
>>>         address 192.168.45.91
>>>          netmask 255.255.255.0
>>>          network 192.168.45.0
>>>          broadcast 192.168.45.255
>>>          ovs_type OVSBridge
>>>          ovs_ports vlan100
>>>
>>> allow-xenbr1 vlan100
>>> iface vlan100 inet manual
>>>          ovs_bridge xenbr1
>>>          ovs_type OVSIntPort
>>>          ovs_options tag=100
>>>          ovs_extra set interface ${IFACE} external-ids:iface-id=$(hostname
>>> -s)
> Without applying the below mentioned patch, does your problem go away
> if you remove all the 'auto' for xenbr0 and xenbr1 also?

Thanks for your reply.
I removed all auto and now works also without backports other patches.
Then ovs networks starts automatically on boot also without "auto", is
it correct?

>>
>> For have it working I had to do "service networking restart".
>> I found probably final solution applying also this patch:
>> http://git.openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=commitdiff;h=9a8b5cc1a3d941c0e33f3f5b5ac260a35a8130af
> The above patch adds the ability to configure OVS with 'auto'
> configured and additionally has the following information:
> """
> Notes on dependencies:
> ---------------------
>
> openvswitch-switch depends on $network, $named $remote_fs and $syslog to start.
> This creates some startup dependency issues.
>
> * Since openvswitch utilities are placed in /usr and /usr can be mounted
> through NFS, openvswitch has to start after it.  But if a user uses openvswitch
> for all his networking needs and hence to mount NFS, there will be a deadlock.
> So, if /usr is mounted through NFS and openvswitch is used for all networking,
> the administrator should figure out a way to mount NFS before starting OVS.
> One way to do this is in initramfs.
>
> * Since openvswitch starts after $network, $remote_fs and $syslog, any startup
> script that depends on openvswitch but starts before it, needs to be changed
> to depend on openvswitch-switch too.
>
> * Ideally, an admin should not add openvswitch bridges in the 'auto'
> section of the 'interfaces' file.  This is because, when ifupdown starts
> working on bridges listed in 'auto', openvswitch has not yet started.
>
> But, if the admin wants to go down this route and adds openvswitch bridges
> in the 'auto' section, openvswitch-switch will forcefully be started when
> ifupdown kicks in. In a case like this, the admin needs to make sure that /usr
> has already been mounted and that a remote $syslog (if used) is ready to
> receive openvswitch logs.
> """
>
>
>> Even if seems not good in some cases.
> Does the above explanation give any hints on why it wouldn't work in some cases?
Yes

>
>> I don't know if also Jessie have this problem but probably yes. If yes I
>> think this bug is only partially solves with 2.3.0+git20140819-3.
>>
>>
>>
>> I had also another start problem probably not related to this, after some
>> hours xenbr0 stopped to working.
>> I not found any useful errors about in logs, only some strange thing, in
>> ifconfig xenbr0 was without the static ip, in syslog keep tried to acquire
>> configuration with dhcp failing (dhcp server present and working in lan).
>> After "service networking restart" was working again but I not understand
>> was happen and why :(
>> Someone have any idea about?
>>
>>
>>
>> Thanks for any reply and sorry for my bad english.
>> _______________________________________________
>> dev mailing list
>> [hidden email]
>> http://openvswitch.org/mailman/listinfo/dev


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]