yahoo-eng-team team mailing list archive

[LIU Yulong <yulong@xxxxxxxxxxxxx>]

According to Rodolfo's explanation, so we can close this bug.

** Changed in: neutron
       Status: Triaged => Fix Released

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

Title:
  DVR and floating IPs broken in latest 7.0.0.0rc1?

Status in kolla-ansible:
  New
Status in neutron:
  Fix Released

Bug description:
  Kolla-Ansible 7.0.0.0rc1 with binary image build (since the source
  option is failing to build ceilometer images currently) on CentOS 7.5
  (latest updates)

  What worked previously does not appear to work anymore.  I'm not sure
  if this is due to an update in CentOS 7.5 or OVS or other at this
  stage, but compute nodes are no longer ARP replying to ARP requests
  for who has the floating IP.

  For testing, I looked for the IP assigned to the FIP namespace's fg
  interface (in my case, fg-ba492724-bd).  This appears to be an IP on
  the ext-net network, but is not the floating IP assigned to a VM.
  Let's call this A.A.A.A and the floating IP B.B.B.B.

  I can tcpdump traffic on the physical port of the compute node and see
  the ARP requests for both A.A.A.A and B.B.B.B with respective pings
  from the Internet, but no ARP replies.

  I have attached a diagram showing, what I believe to be, the correct
  path for the packets.

  There appears to be something broken between my two arrows.

  Since tcpdump is not installed in the openvswitch_vswitchd container,
  nor is ovs-tcpdump, I can't figure out how to mirror and sniff ports
  on the br-ex and br-int bridges, at least in a containerized instance
  of OVS.  If anyone knows a way to do this, I would really appreciate
  the help.

  I haven't found any issues in the OVS configuration (ovs-vsctl show) -
  which matches the attached diagram.

  Has anyone else had issues?

  OVS returns this version info:
  ovs-vsctl (Open vSwitch) 2.9.0
  DB Schema 7.15.1

  in case it helps.

  Eric

To manage notifications about this bug go to:
https://bugs.launchpad.net/kolla-ansible/+bug/1792493/+subscriptions