[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[saleh salah]

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:
  openvswitch systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Premysl Kouril]

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 network-pre.target from After to Before clause.

-- 
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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Kathryn Morgan]

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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Corey Bryant]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Dale Noe]

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 systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Corey Bryant]

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.
https://bugs.launchpad.net/bugs/1448254

Title:
  openvswitch systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Hervé BRY]

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.
https://bugs.launchpad.net/bugs/1448254

Title:
  openvswitch systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Damian Cikowski]

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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Elias Abacioglu]

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 networking.

Here are the logs from a broken system.
```
Sep 12 16:11:07 vm10 systemd[1]: Reached target Network.
Sep 12 16:11:07 vm10 systemd[1]: networking.service: Failed with result 
'exit-code'.
Sep 12 16:11:07 vm10 systemd[1]: networking.service: Unit entered failed state.
Sep 12 16:11:07 vm10 systemd[1]: Failed to start Raise network interfaces.
Sep 12 16:11:07 vm10 systemd[1]: networking.service: Main process exited, 
code=exited, status=1/FAILURE
Sep 12 16:11:07 vm10 ntpdate[3027]: no servers can be used, exiting
Sep 12 16:11:07 vm10 ifup[2858]: Failed to bring up br0.
Sep 12 16:11:07 vm10 ifup[2858]: Cannot find device "br0"
Sep 12 16:11:07 vm10 ifup[2858]: Failed to bring up mgm.
Sep 12 16:11:07 vm10 ifup[2858]: Cannot find device "mgm"
Sep 12 16:11:07 vm10 ifup[2858]: mgm: ERROR while getting interface flags: No 
such device
Sep 12 16:11:07 vm10 ifup[2858]: ovs-vsctl: unix:/var/run/openvswitch/db.sock: 
database connection failed (No such file or directory)
Sep 12 16:11:07 vm10 ovs-vsctl[2991]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
Sep 12 16:11:07 vm10 ovs-vsctl[2991]: ovs|1|vsctl|INFO|Called as ovs-vsctl 
--timeout=5 -- --may-exist add-port br0 mgm vlan_mode=access -- set Interface 
mgm type=internal -- set interface mgm external-ids:iface-id=vm10-mgm-vif
Sep 12 16:11:07 vm10 ifup[2858]: Failed to bring up bond0.
Sep 12 16:11:07 vm10 ifup[2858]: Cannot find device "bond0"
Sep 12 16:11:07 vm10 kernel: bnx2x :01:00.1 em2: NIC Link is Up, 1 Mbps 
full duplex, Flow control: none
Sep 12 16:11:06 vm10 kernel: bnx2x :01:00.1 em2: using MSI-X  IRQs: sp 50  
fp[0] 52 ... fp[7] 59
Sep 12 16:11:06 vm10 kernel: bnx2x :01:00.0 em1: NIC Link is Up, 1 Mbps 
full duplex, Flow control: none
Sep 12 16:11:06 vm10 kernel: bnx2x :01:00.0 em1: using MSI-X  IRQs: sp 39  
fp[0] 41 ... fp[7] 48
Sep 12 16:11:05 vm10 ifup[2858]: bond0: ERROR while getting interface flags: No 
such device
Sep 12 16:11:05 vm10 ifup[2858]: ovs-vsctl: unix:/var/run/openvswitch/db.sock: 
database connection failed (No such file or directory)
Sep 12 16:11:05 vm10 ovs-vsctl[2922]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
Sep 12 16:11:05 vm10 ovs-vsctl[2922]: ovs|1|vsctl|INFO|Called as ovs-vsctl 
--timeout=5 -- --fake-iface add-bond br0 bond0 em1 em2 
vlan_mode=native-untagged bond_mode=balance-tcp lacp=active 
other_config:lacp-time=fast --
Sep 12 16:11:05 vm10 ifup[2858]: ovs-vsctl: unix:/var/run/openvswitch/db.sock: 
database connection failed (No such file or directory)
Sep 12 16:11:05 vm10 ovs-vsctl[2908]: 
ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database 
connection failed (No such file or directory)
Sep 12 16:11:05 vm10 ovs-vsctl[2908]: ovs|1|vsctl|INFO|Called as ovs-vsctl 
--timeout=5 -- --may-exist add-br br0 --
Sep 12 16:11:05 vm10 systemd[1]: Starting Raise network interfaces...
```

-- 
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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Elias Abacioglu]

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 ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Thomas Kaergel]

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 enslaved by ovs...

 The patched unit-file is working fine now.

-- 
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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Thomas Kaergel]

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 interfaces do not get attached to
the openvswitch-bridges, but the system shutdown is working fine. Looks
like ifup@ is turning the interfaces on before openvswitch consumes
them.

I tried playing with the unit-dependencies, but so far without luck.

Is there already a bug report for xenial regarding this issue? I think
it is a good idea to open bug against xenial, don't you think?

-- 
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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Nicolas SCHWARTZ]

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 interface in the /etc/network/interfaces
E.g.: 
allow-ovs main_sw
auto main_sw
iface main_sw inet manual
ovs_type OVSBridge
-Reboot your computer
-Look at journalctl -b0 -r.

The new patched systemd unit nonetwork for zesty works well on 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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Brian Turek]

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 a charm. Without it my server would never try to get a DHCP
lease on startup but ifup worked fine once the machine was up.

I tried to recreate using a VM but the VM has no such issue; it grabs a
DHCP lease without any problems.  I don't know if it's some weird race
condition or what.

-- 
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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[James Page]

** 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.
https://bugs.launchpad.net/bugs/1448254

Title:
  openvswitch systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[James Page]

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, 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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[James Page]

** 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 network interface for server using openvswitch eni syntax; 
reboot server (will take 4 minutes to boot).
+ 
+ [Regression Potential]
+ Medium risk - this is a change to the behaviour of the systemd units, but it 
does appear to have been validated by the wider community.
+ 
+ [Original Bug Report]
+ After upgrade to vivid, my system takes nearly 4 minutes to boot. This 
appears to be related to the new systemd unit ordering.
  
  [Unit]
  Description=Open vSwitch
  After=network.target openvswitch-nonetwork.service
  ...
  
  root@mystic:/lib/systemd/system# systemd-analyze blame | head
-   2min 233ms ifup-wait-all-auto.service
+   2min 233ms ifup-wait-all-auto.service
  ...
  
  Open vSwitch is being started after the network, but the network needs
  Open vSwitch to start since my host traffic is flowing through the
  bridge:
  
  root@mystic:/lib/systemd/system# ovs-vsctl show
  838a8aa4-4811-447d-8dcc-dbb675b78968
- Bridge "br0"
- Port "br0"
- tag: 1
- Interface "br0"
- type: internal
- Port "vlan121"
- tag: 121
- Interface "vlan121"
- type: internal
- Port "eth0"
- tag: 1
- Interface "eth0"
- ovs_version: "2.3.1"
+ Bridge "br0"
+ Port "br0"
+ tag: 1
+ Interface "br0"
+ type: internal
+ Port "vlan121"
+ tag: 121
+ Interface "vlan121"
+ type: internal
+ Port "eth0"
+ tag: 1
+ Interface "eth0"
+ ovs_version: "2.3.1"
  
  The interfaces do eventually start correctly, but only after the long
  timeout above.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openvswitch-switch 2.3.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  Date: Fri Apr 24 14:10:19 2015
  EcryptfsInUse: Yes
  ProcEnviron:
-  TERM=screen
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=screen
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: openvswitch
  UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago)

-- 
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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[James Page]

@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, 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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Simon Leinen]

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 manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Launchpad Bug Tracker]

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 prior to configuration
of any network interfaces (LP: #1448254).  Thanks to Mark Dunn for
this fix.

 -- James Page   Tue, 15 Nov 2016 14:15:06 +

** Changed in: openvswitch (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[James Page]

** 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: openvswitch (Ubuntu Yakkety)
   Status: New => Triaged

** Changed in: openvswitch (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: openvswitch (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: openvswitch (Ubuntu Yakkety)
   Importance: Undecided => High

** Changed in: openvswitch (Ubuntu Zesty)
   Importance: Critical => High

** Changed in: openvswitch (Ubuntu Zesty)
   Status: Triaged => Fix Committed

** Changed in: openvswitch (Ubuntu Zesty)
 Assignee: (unassigned) => James Page (james-page)

-- 
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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Brian Turek]

** 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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Brian Turek]

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 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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Mark Dunn]

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 all sorts of looping dependencies occur doh!
DefaultDependencies=no

#precedants pulled from isup@ service requirements
After=apparmor.service local-fs.target systemd-tmpfiles-setup.service

#subsequent to this service we need the network to start 
Wants=network-pre.target openvswitch-switch.service
Before=network-pre.target openvswitch-switch.service

[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=-/etc/default/openvswitch-switch
ExecStart=/usr/share/openvswitch/scripts/ovs-ctl start \
  --system-id=random $OPTIONS
ExecStop=/usr/share/openvswitch/scripts/ovs-ctl stop

This pulled up the services and allowed my configuration to work

openvswitch-nonetwork.service
● ├─openvswitch-switch.service
● └─network-pre.target
●   ├─ifup@br-eth2.service
●   ├─ifup@br-ex.service
●   ├─ifup@eth0.service
●   ├─ifup@ovs-system.service
●   ├─networking.service
●   └─network.target
● ├─mysql.service
● ├─openvswitch-switch.service
● ├─rabbitmq-server.service
● ├─rc-local.service
● ├─ssh.service
● └─network-online.target
●   ├─apache2.service
●   ├─dns-clean.service
●   └─kerneloops.service

(the dots are green :) )

There is lots of noise on the net about chickens and eggs, so I do not know if 
it solves some other case
The thing that took me so long to solve it (besides unfamiliarity of systemd) 
was the AUTOMATIC inclusion of dependencies, who on earth dreamt that up?

-- 
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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Mark Dunn]

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 all sorts of looping dependencies occur doh!
DefaultDependencies=no

#precedants pulled from isup@ service requirements
After=apparmor.service local-fs.target systemd-tmpfiles-setup.service

#subsequent to this service we need the network to start 
Wants=network-pre.target openvswitch-switch.service
Before=network-pre.target openvswitch-switch.service

[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=-/etc/default/openvswitch-switch
ExecStart=/usr/share/openvswitch/scripts/ovs-ctl start \
  --system-id=random $OPTIONS
ExecStop=/usr/share/openvswitch/scripts/ovs-ctl stop

This pulled up the services and allowed my configuration to work

openvswitch-nonetwork.service
● ├─openvswitch-switch.service
● └─network-pre.target
●   ├─ifup@br-eth2.service
●   ├─ifup@br-ex.service
●   ├─ifup@eth0.service
●   ├─ifup@ovs-system.service
●   ├─networking.service
●   └─network.target
● ├─mysql.service
● ├─openvswitch-switch.service
● ├─rabbitmq-server.service
● ├─rc-local.service
● ├─ssh.service
● └─network-online.target
●   ├─apache2.service
●   ├─dns-clean.service
●   └─kerneloops.service

(the dots are green :) )

There is lots of noise on the net about chickens and eggs, so I do not know if 
it solves some other case
The thing that took me so long to solve it (besides unfamiliarity of systemd) 
was the AUTOMATIC inclusion of dependencies, who on earth dreamt that up?

-- 
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:
  openvswitch systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Alberto Salvia Novella]

** 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.net/bugs/1448254

Title:
  openvswitch systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Alberto Salvia Novella]

** 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:
  openvswitch systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Alberto Salvia Novella]

** 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 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:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Alberto Salvia Novella]

** 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 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:
  openvswitch systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1448254/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Launchpad Bug Tracker]

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/bugs/1448254

Title:
  openvswitch systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1448254/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Launchpad Bug Tracker]

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:
  openvswitch systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Mark Dunn]

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 br-eth2 vxlan1 
sudo ovs-vsctl set interface vxlan1 type=vxlan options:remote_ip=192.168.102.205
sudo ovs-vsctl add-port br-eth2 vxlan2 
sudo ovs-vsctl set interface vxlan2 type=vxlan options:remote_ip=192.168.102.234
sudo ovs-vsctl add-br br-ex
sudo ovs-vsctl add-port br-ex eth0

then bring up the network from /etc/network/interfaces with

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual
up ifconfig $IFACE 0.0.0.0 up
up ip link set $IFACE promisc on
down ip link set $IFACE promisc off 
down ifconfig $IFACE down

auto br-ex
iface br-ex inet static
address 192.168.102.206
netmask 255.255.255.0
gateway 192.168.102.36
dns-nameservers 192.168.102.10 192.168.102.50
up ip link set $IFACE promisc on
down ip link set $IFACE promisc off

auto br-eth2
iface br-eth2 inet static
address 10.1.0.11
netmask 255.255.255.0
up ip link set $IFACE promisc on
down ip link set $IFACE promisc off 
mtu 1446


from sudo systemctl list-unit-files i get 

openvswitch-nonetwork.service  static  
openvswitch-switch.service enabled 

so I assume they are running

-- 
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:
  openvswitch systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1448254/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Mark Dunn]

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 br-eth2 vxlan1 
sudo ovs-vsctl set interface vxlan1 type=vxlan options:remote_ip=192.168.102.205
sudo ovs-vsctl add-port br-eth2 vxlan2 
sudo ovs-vsctl set interface vxlan2 type=vxlan options:remote_ip=192.168.102.234
sudo ovs-vsctl add-br br-ex
sudo ovs-vsctl add-port br-ex eth0

then bring up the network from /etc/network/interfaces with

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual
up ifconfig $IFACE 0.0.0.0 up
up ip link set $IFACE promisc on
down ip link set $IFACE promisc off 
down ifconfig $IFACE down

auto br-ex
iface br-ex inet static
address 192.168.102.206
netmask 255.255.255.0
gateway 192.168.102.36
dns-nameservers 192.168.102.10 192.168.102.50
up ip link set $IFACE promisc on
down ip link set $IFACE promisc off

auto br-eth2
iface br-eth2 inet static
address 10.1.0.11
netmask 255.255.255.0
up ip link set $IFACE promisc on
down ip link set $IFACE promisc off 
mtu 1446


from sudo systemctl list-unit-files i get 

openvswitch-nonetwork.service  static  
openvswitch-switch.service enabled 

so I assume they are running

-- 
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:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Kevin Otte]

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 systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1448254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

[Kevin Otte]

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:
  openvswitch systemd unit file ordering wrong

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1448254/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs