← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1931696] Re: ovs offload broken from neutron 16.3.0 onwards

 

Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.

** Changed in: neutron (Ubuntu Impish)
       Status: New => Won't Fix

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

Title:
  ovs offload broken from neutron 16.3.0 onwards

Status in OpenStack Neutron Open vSwitch Charm:
  Fix Released
Status in Ubuntu Cloud Archive:
  New
Status in Ubuntu Cloud Archive queens series:
  New
Status in Ubuntu Cloud Archive rocky series:
  New
Status in Ubuntu Cloud Archive stein series:
  New
Status in Ubuntu Cloud Archive train series:
  New
Status in Ubuntu Cloud Archive ussuri series:
  New
Status in Ubuntu Cloud Archive victoria series:
  New
Status in Ubuntu Cloud Archive wallaby series:
  New
Status in Ubuntu Cloud Archive xena series:
  New
Status in neutron:
  In Progress
Status in neutron package in Ubuntu:
  New
Status in neutron source package in Bionic:
  New
Status in neutron source package in Focal:
  New
Status in neutron source package in Hirsute:
  Won't Fix
Status in neutron source package in Impish:
  Won't Fix

Bug description:
  The 16.3.0 release of neutron introduced patch [1] which breaks the
  use of non-offloaded ports on a node that has ovs offload enabled. Our
  setup is as follows:

    * single tenant network (vxlan)
    * two vms with one port each where one port has offload enabled and the other does not
    * from non-offloaded vm I am unable to ping my gateway and I see the following:

  # grep dropping /var/log/openvswitch/ovs-vswitchd.log 
  2021-06-11T09:37:16.271Z|00553|ofproto_dpif_xlate(handler150)|WARN|dropping VLAN 1 tagged packet received on port qr-446b3a35-d0 configured as VLAN 1 access port on bridge br-int while processing recirc_id=0x1a,ct_state=est|rpl|trk,ct_zone=1,ct_nw_src=172.16.0.126,ct_nw_dst=172.16.0.1,ct_nw_proto=1,ct_tp_src=8,ct_tp_dst=0,eth,icmp,in_port=3,vlan_tci=0x0000,dl_src=fa:16:3e:66:e8:2f,dl_dst=fa:16:3e:3c:50:c1,nw_src=172.16.0.1,nw_dst=172.16.0.126,nw_tos=0,nw_ecn=0,nw_ttl=64,icmp_type=0,icmp_code=0

  which is from [2]. The patch [1] is configurable by settig
  explicitly_egress_direct=True in
  /etc/neutron/plugins/ml2/openvswitch_agent.ini and that has fixed
  connectivity for me so I am going to submit a patch to make this
  configurable via the charm.

  [1] https://opendev.org/openstack/neutron/commit/d865165cc8cbd50a3e79a25065ef9a310d7c9396
  [2] https://github.com/openvswitch/ovs/blob/branch-2.13/ofproto/ofproto-dpif-xlate.c#L2220

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1931696/+subscriptions