Bug#771863: [ovs-dev] Bug#771863: [PKG-Openstack-devel] Bug#771863: Bug#771863: Service does not start or parse interfaces correctly
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
d...@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771863: [ovs-dev] Bug#771863: Service does not start or parse interfaces correctly, updating severity
On Sat, Dec 13, 2014 at 2:03 AM, Stig Sandbeck Mathisen s...@debian.org wrote: Gurucharan Shetty shet...@nicira.com writes: I haven't looked at what needs to be done to handle those statements. I welcome a patch, preferably sent to d...@openvswitch.org after reading the CONTRIBUTING.md in the openvswitch repo. I assume the openvswitch repo is at https://github.com/openvswitch/ovs Do you use GitHub pull requests at all, or prefer just formatted patches to the mailing list? We haven't handled GitHub pull requests so far. It does not fit well with our current way of code-reviewing. We would very much prefer code sent to d...@openvswitch.org using git format-patch and git send-email (you can experiment by sending a mail to yourself and apply it with 'git am') I would like to clarify that 2.3.1 does get rid of the check on $RUNLEVEL which was the original bug description. That's great, thanks. :) I probably should treat this as a separate bug. Would you like me to file a new bug for it in the Debian BTS, in addition to submitting an upstream patch? I am not the maintainer of the project at debian. Ben Pfaff is the maintainer. I only made a comment because I wrote the first version of integration of 'interfaces' with openvswitch and wanted to clarify that it has been fixed in 2.3.1 as a data point for the maintainer. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771863: [ovs-dev] Bug#771863: openvswitch-switch: Patch update, handle interface files sourced from /etc/network/interfaces
On Tue, Dec 9, 2014 at 12:12 AM, Stig Sandbeck Mathisen s...@debian.org wrote: Package: openvswitch-switch Version: 2.3.0+git20140819-2 Followup-For: Bug #771863 Dear Maintainer, The network_interfaces() function in the /etc/init.d/openvswitch-switch script also does not handle source or source-directory statements in /etc/network/interfaces. Fwiw, this is has been fixed in OVS 2.3.1. Please consider the attached patch which, including the first problem in this bug, also uses the ifquery command to list available bridges. The ifquery command is from the ifupdown package. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openvswitch-switch depends on: ii kmod 18-3 ii libatomic1 4.9.1-19 ii libc6 2.19-13 ii libpython2.7-stdlib [python-argparse] 2.7.8-11 ii libssl1.0.01.0.1j-1 ii netbase5.3 ii openvswitch-common 2.3.0+git20140819-2 ii procps 2:3.3.9-8 pn python:any none ii uuid-runtime 2.25.2-3 openvswitch-switch recommends no packages. openvswitch-switch suggests no packages. -- Configuration Files: /etc/init.d/openvswitch-switch changed [not included] -- no debconf information ___ dev mailing list d...@openvswitch.org http://openvswitch.org/mailman/listinfo/dev -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#771863: [ovs-dev] Bug#771863: Service does not start or parse interfaces correctly, updating severity
My previous reply did not do a good job with the context. It made it look like OVS 2.3.1 handles source or source-directory statements. That is not correct, it does not handle those statements. I haven't looked at what needs to be done to handle those statements. I welcome a patch, preferably sent to d...@openvswitch.org after reading the CONTRIBUTING.md in the openvswitch repo. I would like to clarify that 2.3.1 does get rid of the check on $RUNLEVEL which was the original bug description. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686518: [PATCH] debian: Don't depened on $RUNLEVEL at startup to create bridges.
On Fri, Sep 12, 2014 at 1:22 AM, Philipp S. Schmidt ph...@in-panik.de wrote: The patch below fixes the problem for me - Thanks I applied the patch to master branch and 2.3 branch of OVS repo found here: https://github.com/openvswitch/ovs I suppose Ben will eventually upload it to debian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#686518: [ovs-dev] Bug#686518: network_interfaces() does not work with systemd
On Thu, Sep 11, 2014 at 4:04 AM, Philipp S. Schmidt ph...@in-panik.de wrote:
It seems that most of the problem is fixed in the recent version
as ifup --allow=ovs [bridges…]” is called in the network_interfaces()
function.
Sadly, when using systems, this function just return and does not
execute ifup as ${RUNLEVEL} is not set.
I have no idea what purpose the line [ -z ${RUNLEVEL} ] return”
in network_interfaces has, but it prevents this bug from being fixed
when systemd is used as init :(
[ -z ${RUNLEVEL} ] return is there to prevent OVS interfaces
from being destroyed and recreated when someone does a
/etc/init.d/openvswitch-switch restart. It looks like it does not
get set for systemd during startup.
I sent a patch to fix this:
http://openvswitch.org/pipermail/dev/2014-September/045570.html
___
dev mailing list
d...@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
