[NETVIRT-420] Avoid creating auto-tunnels for VLAN tenant networks Created: 11/Jan/17  Updated: 10/Mar/17  Resolved: 10/Mar/17

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

Type: Bug
Reporter: Sridhar Gaddam Assignee: Sridhar Gaddam
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 7520

 Description   

Setup:
In a Multi-node setup with a controller node (running dhcp-agent) and one or more compute nodes.

Steps:
1. Create a Neutron Router.
2. Create a tenant VLAN network.
3. Create an IPv4 subnet in the tenant VLAN network.
4. Associate the subnet to the Neutron router.
5. Spawn a VM on one of the compute nodes.

Observations: A VxLAN tunnel is setup between the Controller node (running dhcp-agent) and Compute node (hosting the VM).
This is creating issues in VM acquiring the IP address.

Expected behavior: When using a VLAN tenant network, auto-tunnel code of Netvirt should NOT be creating any VxLAN tunnels.

 Comments   
Comment by Sridhar Gaddam [ 11/Jan/17 ]

Patch that addresses this issue:
https://git.opendaylight.org/gerrit/#/c/50268/

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