The way of configuring /etc/network/interfaces* seems to be changed.
https://github.com/openvswitch/ovs/blob/master/debian/openvswitch-switch.README.Debian
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Ubuntu 14.04.5 (Open vSwitch) 2.0.2 (installed with apt install
openvswitch-switch)
Following configuration works for me, also after reboot:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback n
confirmed this bug on ubuntu 14.04.5 (ovs 2.5.9, openstack mitaka):
### ifcfg-br-mesh ###
auto br-mesh
allow-ovs br-mesh
iface br-mesh inet static
ovs_type OVSBridge
ovs_ports ens5
address 192.168.2.4/24
ovs_extra set Bridge br-mesh datapath_type=netdev
### ifcfg-ens5 ###
allow-br-mesh ens5
iface
* Ubuntu 14.04.4 + Openstack Liberty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based interfaces not started in time during boot
To manage notifications about this bug
I have the same bug too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based interfaces not started in time during boot
To manage notifications about this bug go to:
https
Mee too. Ubuntu 14.04 + Openstack Kilo. Br-eth1 is not starting on system boot
but if I do `ifup br-eth1` all things are doing well.
# grep -vE "(^#|^$)" /etc/network/interfaces.d/ovs-bridge.cfg
iface eth0 inet manual
iface eth1 inet manual
auto br-eth1
allow-ovs br-eth1
iface br-eth1 inet static
I still see this bug in openstack kilo on ubuntu trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based interfaces not started in time during boot
To manage notifica
root@red-compute:~# ovs-vsctl show
8d08d8e4-49f2-4243-b1db-7641984a8530
Bridge br-ex
Port br-ex
Interface br-ex
type: internal
Bridge br-int
Port "eth1"
Interface "eth1"
Port br-int
Interface br-int
I will open another bug... sorry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based interfaces not started in time during boot
To manage notifications about this bug go
You should reopen it since it happens in trusty tahr to me.
Someone can try it in this version of ubuntu, please?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based inte
This bug was fixed in the package openvswitch -
1.10.1+git20130823-0ubuntu2
---
openvswitch (1.10.1+git20130823-0ubuntu2) saucy; urgency=low
* Fully support transitions from openvswitch module in 3.11 kernel to
DKMS module:
- d/openvswitch-switch.openvswitch-force-reload-mod
** Branch linked: lp:ubuntu/saucy-proposed/openvswitch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based interfaces not started in time during boot
To manage notificati
** Branch linked: lp:~james-page/ubuntu/saucy/openvswitch/snapshot-1.11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based interfaces not started in time during boot
To
** Branch linked: lp:~james-page/ubuntu/saucy/openvswitch/1.12-snapshot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based interfaces not started in time during boot
To
@Jesse & Matteo
I'm not comfortable backporting this to the version in 12.04 - however,
I can offer a compromise.
OpenvSwitch 1.10 will be included in the Cloud Archive for OpenStack
Havana on 12.04 and would include this fix (assuming I can get in enough
testing this week to satisfy myself that
I second @jesse-pretorius' request: the upstart job definitely needs to
be backported to Precise once it hits Saucy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based int
** Changed in: openvswitch (Ubuntu Saucy)
Status: In Progress => Triaged
** No longer affects: openvswitch (Ubuntu Saucy)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvsw
@james-page We're testing your upstart openvswitch-switch.conf file on
Precise. It's looking good so far. Can this bug be marked as relevant
for Precise too, please? Once it's in Saucy we'd definitely like to see
it backported to Precise.
--
You received this bug notification because you are a me
Pushing the milestone for this bug out a bit; the init script does alot
more that just start/stop openvswitch so needs more careful
consideration.
** Changed in: openvswitch (Ubuntu Saucy)
Milestone: ubuntu-13.05 => ubuntu-13.07
--
You received this bug notification because you are a member
Attaching the upstart configuration I'm proposing to upload to saucy
once I get 3.9 kernel compat sorted out for the DKMS packages.
** Attachment added: "openvswitch-switch.conf"
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028/+attachment/3678528/+files/openvswitch-switch.up
I can confirm this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based interfaces not started in time during boot
To manage notifications about this bug go to:
https
** Also affects: openvswitch (Ubuntu Saucy)
Importance: High
Status: Confirmed
** Changed in: openvswitch (Ubuntu Saucy)
Assignee: (unassigned) => James Page (james-page)
** Changed in: openvswitch (Ubuntu Saucy)
Status: Confirmed => In Progress
** Changed in: openvswitch (
I am doing some research regarding this issue and found a proposal for
Open vSwitch upstart script:
https://github.com/gdahlm/openvswitch/blob/ubuntu/debian/openvswitch.upstart
The discussion about this is located at
http://openvswitch.org/pipermail/dev/2012-May/017010.html
So far, I've applied
This bug also prevents starting some services (e.g. isc-dhcp-server) on
openvswitch interfaces at boot.
I avoided the problem by changing /etc/network/interfaces such that ovs
interfaces don't come up automatically, and ifupping them manually in
/etc/rc.local instead... but that's pretty silly.
-
** Changed in: openvswitch (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1084028
Title:
openvswitch based interfaces not started in time during boot
To mana
I'm not confident enough to mark it Confirmed, but I believe that's
right - an upstart job is needed.
** Changed in: openvswitch (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
26 matches
Mail list logo
