Sorry, lost track of the bug as it fell into 100 papercuts...
if it helps I solved my ordering problem by modifying the
/lib/systemd/sysytem/openvswitch-nonetwork.service
as follows
[Unit]
Description=Open vSwitch Internal Unit
PartOf=openvswitch-switch.service
# Without this
** Changed in: openvswitch (Ubuntu)
Status: Confirmed => Triaged
** Changed in: hundredpapercuts
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.n
** Changed in: openvswitch (Ubuntu)
Importance: Undecided => Critical
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: New => Confirmed
** Changed in: hundredpapercuts
Importance: Undecided => Critical
--
You rec
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openvswitch (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net
I have a the same problem.
In systemd, there are two files openvswitch-nonetwork.service
openvswitch-switch.service which are supposed to fix this problem
I am testing OpenStack with VXLAN and require
sudo ovs-vsctl add-br br-eth2
sudo ovs-vsctl set port br-eth2 tag=2001
sudo ovs-vsctl add-port
Looks we've been through this before with upstart:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1084028
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
