yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1492228@xxxxxxxxxxxxxxxxxx>]

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

** Changed in: neutron
       Status: Incomplete => Expired

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

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

Status in neutron:
  Expired

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

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