SR-IOV port doesn't reach OVS port on same compute node

Bug #1492228 reported by Pedro Sousa
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
neutron
Low
edan david

Bug Description

Hi,

I'm using Neutron Kilo with openvswitch and sriovnicswitch mechanism driver in ml2 plugin.

Everything works fine, except I cannot reach ovs port instance from sr-iov port instance and vice-versa, that reside on the same compute node, that uses a br-int bridge. In different compute nodes it works fine, but my understanding in this configuration is that it uses an physical interface bridge, br-p2p1.

RDO Kilo Centos 7.1

python-neutron-2015.1.1-1.el7.noarch
openstack-neutron-openvswitch-2015.1.1-1.el7.noarch
python-neutronclient-2.4.0-1.el7.noarch
openstack-neutron-ml2-2015.1.1-1.el7.noarch
openstack-neutron-common-2015.1.1-1.el7.noarch
openstack-neutron-2015.1.1-1.el7.noarch
openstack-neutron-sriov-nic-agent-2015.1.1-1.el7.noarch
openvswitch-2.3.1-2.el7.x86_64
kernel-3.10.0-229.11.1.el7.x86_64

Regards,
Pedro Sousa

yujie (16189455-d)
information type: Public → Public Security
yujie (16189455-d)
information type: Public Security → Public
Changed in neutron:
assignee: nobody → Moshe Levi (moshele)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Moshe Levi (<email address hidden>) on branch: master
Review: https://review.openstack.org/198736

Moshe Levi (moshele)
Changed in neutron:
assignee: Moshe Levi (moshele) → nobody
Revision history for this message
yujie (16189455-d) wrote :

I am using neutron kilo without dvr to create sriov instance VM-A,it works well and could connect to its gateway fine.
But when I let the normal instance VM-B which in the same compute-node with VM-A ping its gateway, it failed. I capture the packet on the network-node, find the gateway already reply the ARP-reply message to VM-B. But compute-node which VM-B lives could not send the package to VM-B.
If delete VM-A and set : echo 0 > /sys/class/enp5s0f0/device/sriov_numvfs, the problem solved.

Is it a same question with this bug ?

Revision history for this message
Itzik Brown (itzikb1) wrote :

AFAIK yes.

Brent Eagles (beagles)
Changed in neutron:
assignee: nobody → Brent Eagles (beagles)
Moshe Levi (moshele)
tags: added: sriov-pci-pt
Changed in neutron:
assignee: Brent Eagles (beagles) → Moshe Levi (moshele)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/198736
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

If you are still working on this please resume, or allow someone else to pick this up.

Changed in neutron:
assignee: Moshe Levi (moshele) → nobody
status: In Progress → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/320562

Changed in neutron:
status: Expired → In Progress
Changed in neutron:
importance: Undecided → Low
Changed in neutron:
assignee: nobody → edan david (edand)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/320562
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=2c8f61b816bf531a17a7b45d35a5388e8a2f607a
Submitter: Jenkins
Branch: master

commit 2c8f61b816bf531a17a7b45d35a5388e8a2f607a
Author: Edan David <email address hidden>
Date: Tue May 24 11:54:02 2016 -0400

    Adding FDB population agent extension

    The purpose of this extension is updating the FDB table upon changes of
    normal port instances thus enabling communication between direct port
    SR-IOV instances and normal port instances.
    Additionally enabling communication to direct port
    instances with floating ips.
    Support for OVS agent and linux bridge.

    DocImpact
    Change-Id: I61a8aacb1b21b2a6e452389633d7dcccf9964fea
    Closes-Bug: #1492228
    Closes-Bug: #1527991

Changed in neutron:
status: In Progress → Fix Released
tags: added: liberty-backport-potential mitaka-backport-potential
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/neutron 9.0.0.0b2

This issue was fixed in the openstack/neutron 9.0.0.0b2 development milestone.

tags: added: neutron-proactive-backport-potential
Revision history for this message
mkrish004c (murali-krishnaswamy) wrote :

Will this patch works for VLAN network?
 - my scenario
      Create a VLAN network.
      Create a normal instance VM-OVS, the OVS external bridge(br-ex) is connected to PF.
      I am not able to get the IP from external DHCP and i am able to see the fdb entries for the VM MAC.
      Create SRIOV instance VM-SRIOV on the same VLAN network on the same compute host.
      I am able to get IP from external server and do ping gateway for VM-SRIOV via VF.
      Then reboot normal instance VM-OVS and it works once after i create a first SRIOV VM.
      or it works if i clear the VFs in the same compute host.
      But still i am not able to ping each other between VM-OVS and VM-SRIOV

Revision history for this message
mkrish004c (murali-krishnaswamy) wrote :

Added to that,

The TCP dump shows the reply going out of the DHCP server, but it is not hitting PF but the ARP is received at the VF and hit the SRIOV instance VM-SRIOV.

PF is not getting any incoming packets from external server or from SRIOV instance.

tags: removed: neutron-proactive-backport-potential
Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

Murali, if you still experience issues with the patch, please report a new bug.

tags: removed: liberty-backport-potential
tags: removed: mitaka-backport-potential
Revision history for this message
Ihar Hrachyshka (ihar-hrachyshka) wrote :

The fix is too invasive to backport it to Mitaka, removing the mitaka-backport-potential tag.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers