we fix it on bionic by following below tutorial: "Boot support (Ubuntu 16.04 –
when using systemd)"
https://www.opencloudblog.com/?p=240
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
The OVS and ifupdown boot order is broken again in Bionic. Why the whole
openvswitch-nonetwork.service unit was removed from Bionic without
appropriate substitute? We have currently fixed it by modifying
openvswitch-switch.service ovs-vswitchd.service and ovsdb-server.service
units by moving
Running into the same issue on Cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
openvswitch systemd unit file ordering wrong
To manage notifications about this bug go to:
Hi Dale,
Please can you let us know what release you hit this on?
Thanks,
Corey
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
openvswitch systemd unit file ordering wrong
To
I ran across this today, apparently still not fixed. I was also
surprised and shocked that netplan.io doesn't support it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
openvswitch
If you use the Ubuntu Cloud Archive, newer versions of Openvswitch are
available backports to xenial. For more details see:
https://wiki.ubuntu.com/OpenStack/CloudArchive
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I agree, this should be backported to Xenial. Bionic does not support
Openvswitch yet through netplan.io, so at least the previous LTS should
support it correctly !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Why it has not been backported to Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
openvswitch systemd unit file ordering wrong
To manage notifications about this bug go to:
I might as well just add some facts and my logs.
First of all, I have one Xenial node where open vswitch worked, guessing that
that time open vswitch daemon started before trying to setup network.
And then on other machines it doesn't work cause the daemon isn't started
before trying to setup
Can also confirm that Marks patch worked.
This was two years ago, why haven't this been fixed yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
openvswitch systemd unit file
sry, i was wrong. I had some issues in my /etc/network/interfaces-file
which caused the patched unit-file to malfunction. To be more precise: i
did put a line "auto " above any device enslaved by openvswitch-
bridges or -bonds later on. That forced ifup@ to turn the devices on
before they were
I'm also affected by this on ubuntu 16.04. The patched systemd-unit-file
does not work for me.
With the original unit-file the systems starts fine and all bridges and
physical interfaces are configured by openvswitch, but the systems hangs
during shutdown.
With patched unit-file the physical
The bug is still there on ubuntu 16.04
In the journalctl logs openvswitch complains about connecting to its db while
trying to raise NIC defined in the /etc/network/interfaces or
/etc/network/interfaces.d/* and it slow down the process and create errors.
Steps to reproduce:
-Create OVS
James,
This bug seems to be weird to reproduce. My physical Xenial server
worked for months without the proposed patch then last week it suddenly
stopped receiving DHCP lease 2 days ago. After much troubleshooting I
remembered I was on this bug report, used the proposed patch, and it
works like
** Changed in: openvswitch (Ubuntu Yakkety)
Assignee: James Page (james-page) => (unassigned)
** Changed in: openvswitch (Ubuntu Yakkety)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK so I'm struggling a bit to produce a nice /e/n/i that reproduces the
issue on a minimal/fresh install to help with SRU verification - any of
the participants in this bug report have anything we can use for that?
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
- After upgrade to vivid, my system takes nearly 4 minutes to boot. This
- appears to be related to the new systemd unit ordering.
+ [Impact]
+ systems with openvswitch management primary network devices take a long time
to boot.
+
+ [Test Case]
+ Configure primary
@Simon
Working on the backports
** Changed in: openvswitch (Ubuntu Yakkety)
Assignee: (unassigned) => James Page (james-page)
** Changed in: openvswitch (Ubuntu Yakkety)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks for looking into this. Any chance of getting the fix backported
to Xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
openvswitch systemd unit file ordering wrong
To
This bug was fixed in the package openvswitch - 2.6.1-0ubuntu1
---
openvswitch (2.6.1-0ubuntu1) zesty; urgency=medium
* New upstream point release (LP: #1641956).
* d/openvswitch-switch.openvswitch-nonetwork.service: Update Unit
definition to ensure that openvswitch starts
** Also affects: openvswitch (Ubuntu Zesty)
Importance: Critical
Status: Triaged
** Also affects: openvswitch (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: openvswitch (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in:
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
openvswitch systemd unit file ordering wrong
To manage notifications about this bug go to:
I was one of the people that helped get this fixed in Trusty and now, in
a major case of deja vu, hit this same issue now with Xenial. It looks
like Mark Dunn's fix above matches http://www.opencloudblog.com/?p=240
and I can confirm it fixed the problem on Xenial.
--
You received this bug
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
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
** 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.
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
** 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
** 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
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.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448254
Title:
openvswitch
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
35 matches
Mail list logo
