Bug 1522954 - VMs with non-SRIOV ports don't communicate on different compute nodes
Summary: VMs with non-SRIOV ports don't communicate on different compute nodes
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 10.0 (Newton)
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Jakub Libosvar
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks: 1335596 intelosp10bugs
TreeView+ depends on / blocked
 
Reported: 2017-12-06 19:50 UTC by shivapriya.o.hiremath
Modified: 2018-02-12 18:25 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-12 18:25:15 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
templates used to deploy OSP overcloud with SR-IOV (7.56 KB, application/zip)
2017-12-06 19:50 UTC, shivapriya.o.hiremath
no flags Details
Neutron Logs (302.23 KB, application/zip)
2017-12-12 02:01 UTC, shivapriya.o.hiremath
no flags Details

Description shivapriya.o.hiremath 2017-12-06 19:50:08 UTC
Created attachment 1363882 [details]
templates used to deploy OSP overcloud with SR-IOV

Description of problem:VMs with non-SRIOV ports don't communicate on different compute nodes


Version-Release number of selected component (if applicable): OSP-10 has been installed with SR-IOV templates. 


How reproducible: Always


Steps to Reproduce:
1.Install OSP-10 with SR-IOV
2.Spawn any VM using non-SRIOV ports on 2 different Compute nodes
3.Ping each other

Actual results:
VMs don't ping each other. There is no communication between the VMs with non-SRIOV ports. Whereas VMs with SRIOV ports work fine on different compute nodes.

Expected results:
VMs should ping each other establishing communication between each other.


Additional info:
Attached our template used to deploy OSP overcloud with SR-IOV

Comment 1 Jakub Libosvar 2017-12-11 14:48:23 UTC
Can you please attach neutron and ovs-agent logs from controller and both compute nodes in DEBUG log level?

Comment 2 shivapriya.o.hiremath 2017-12-12 02:01:22 UTC
Created attachment 1366411 [details]
Neutron Logs

Attaching the logs from neutron. 


Note that, the instances don't obtain IP addresses automatically after the instances are launched. 

IP address is assigned manually, but we are still not able to ping between the VMs.

Comment 4 shivapriya.o.hiremath 2018-02-12 18:25:15 UTC
Fixed after adding the physical port in the compute nodes. 
ovs-vsctl add-port <bridge_name> <physical_interface_name>


Note You need to log in before you can comment on or make changes to this bug.