[Bug 1736510] Re: openvswitch and linuxbridge agents should start only after network is ready

[Corey Bryant]

The same issue affects neutron-linuxbridge-agent as reported by Jake Yip
in https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/2032811

** Summary changed:

- openvswitch agent should start only after network is ready
+ openvswitch and linuxbridge agents should start only after network is ready

** Also affects: neutron (Ubuntu Mantic)
   Importance: Medium
       Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1736510

Title:
  openvswitch and linuxbridge agents should start only after network is
  ready

Status in neutron package in Ubuntu:
  Triaged
Status in neutron source package in Mantic:
  Triaged

Bug description:
  During rebooting a node, neutron-openvswitch agent sometimes fails
  directly after booting with a message like

  2017-12-05 13:33:23.793 1388 ERROR
  neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-]
  Tunneling can't be enabled with invalid local_ip '1.2.3.4'. IP
  couldn't be found on this host's interfaces.

  So it seems that it is being started too early, it should wait until
  the static network configuration has been finished. Adding

  "After=network.target"

  to the definition of neutron-openvswitch-agent.service seems to
  mitigate the issue, but perhaps there is a better solution still?

  Affects at least Ocata UCA, not tested on Pike yet.

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