[NETVIRT-1093] Broadcast packet does not reach VM instance on different node Created: 14/Feb/18  Updated: 25/Nov/19  Resolved: 25/Nov/19

Status: Resolved
Project: netvirt
Component/s: None
Affects Version/s: None
Fix Version/s: Magnesium

Type: Bug Priority: Medium
Reporter: Bertrand Low Assignee: Bertrand Low
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Tested with karaf-0.7.2-20180207.142346-342.tar.gz

Feature: odl-netvirt-openstack

using devstack

VM instances are created in the same subnet.

Attachments: File COMPUTE.tar.gz     File CONTROL.tar.gz     File ITM-json.tar.gz     File karaf.tar.gz    
Priority: High

 Description   

Tested with karaf-0.7.2-20180207.142346-342.tar.gz

Feature: odl-netvirt-openstack

using devstack

VM instances are created in the same subnet.

The broadcast request packet makes it to all VM instances located on the same node (e.g. openstack control node).

However, VM instances located on a different node than the broadcast originator (e.g. on the compute node) do not receive the broadcast request.

 Comments   
Comment by Bertrand Low [ 21/Feb/18 ]

Attached are logs/info for this bug's scenario using karaf-0.7.2-20180130.170631-330.tar.gz

Conntrack is enabled

1 VM created on Openstack CONTROL, 1 VM created on Openstack COMPUTE.

Steps:

1-stack - using devstack pike
2-createVMs - create 1 VM on CONTROL, create 1 VM on COMPUTE, both on the same subnet
3-createSecurityGroupRules - create security group rules to allow for ssh to the VMs
4-createAllowedAddressPairs - create allowed-address-pairs to allow for multicast packets (this step is not necessary, but is used as part of the environment to test multicast)
5-pingBCfromCONTROL - ping -b 255.255.255.255 from the VM on the CONTROL node
6-pingBCfromCOMPUTE - ping -b 255.255.255.255 from the VM on the COMPUTE node

I've attached the karaf logs (karaf.tar.gz), ITM data objects (ITM-json.tar.gz, retrieved after step 6), and flows/groups/ports on the CONTROL and COMPUTE after each step.

Comment by Sam Hague [ 02/Oct/18 ]

bertrandlow vinh.nguyen@hcl.com is this bug still valid? Still working on it?

Generated at Wed Feb 07 20:23:13 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.