yahoo-eng-team team mailing list archive

[Brian Haley <1810764@xxxxxxxxxxxxxxxxxx>]

I believe we deprecated, then removed, Xen support in neutron in 2020
[0] so I'll close this bug. Please reopen if necessary.

[0]
https://review.opendev.org/q/a6dbf97242caa3be646e8eb6b1502b5e59e123fd

** Changed in: neutron
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1810764

Title:
  rootwrap daemon bypassed - Breaks XenServer

Status in neutron:
  Invalid

Bug description:
  The commit
  https://github.com/openstack/neutron/commit/05a54e800430bcfc81e36e1dad89fa47f3e8a6f0
  appears to break XenServer integration.

  Specifically,
  https://github.com/openstack/neutron/commit/05a54e800430bcfc81e36e1dad89fa47f3e8a6f0#diff-6a3c59b7b71c12cc29eca4c85268864eR1348
  appears to run exclusively in the context of Nova - however in
  XenServer, the IP address for the tunnel is in dom0.  XenServer's
  agent will redirect the actual OVS command to dom0 so the local IP
  address check is not valid.

  We therefore fail with ERROR
  neutron.plugins.ml2.drivers.openvswitch.agent.ovs_neutron_agent [-]
  Tunneling can't be enabled with invalid local_ip '10.62.65.37'. IP
  couldn't be found on this host's interfaces.

  XenServer uses a rootwrap helper - https://github.com/openstack/os-
  xenapi/blob/master/devstack/plugin.sh#L148

  I think the bug may be that we can't use privileged.get_ip_addresses
  but instead need to use agent_utils.execute to obtain the IP addresses

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