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

Jake Yip 1736510 at bugs.launchpad.net
Wed Aug 28 10:22:52 UTC 2024


Hi Corey,

FYI the neutron-linuxbridge-agent.neutron-linuxbridge-cleanup.service.in
file needs a similar patch. I've attached logs for when it runs before
network is online


neutron-linuxbridge-cleanup[3695]:   File "/usr/lib/python3/dist-packages/dns/resolver.py", line 734, in __init__
neutron-linuxbridge-cleanup[3695]:     self.read_resolv_conf(filename)
neutron-linuxbridge-cleanup[3695]:   File "/usr/lib/python3/dist-packages/dns/resolver.py", line 785, in read_resolv_conf
neutron-linuxbridge-cleanup[3695]:     raise NoResolverConfiguration
neutron-linuxbridge-cleanup[3695]: dns.resolver.NoResolverConfiguration: Resolver configuration could not be read or specified no nameservers.
systemd[1]: neutron-linuxbridge-cleanup.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: neutron-linuxbridge-cleanup.service: Failed with result 'exit-code'.
systemd[1]: Failed to start OpenStack Neutron Linux bridge cleanup.

-- 
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:
  Fix Released
Status in neutron source package in Mantic:
  Fix Released

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




More information about the Ubuntu-openstack-bugs mailing list