RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1030501 - Neutron VLAN tenant networks don't work on some hardware
Summary: Neutron VLAN tenant networks don't work on some hardware
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: RDO
Classification: Community
Component: kernel
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Flavio Leitner
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-14 15:14 UTC by Matthew Mosesohn
Modified: 2014-10-27 11:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-16 13:27:32 UTC
Embargoed:


Attachments (Terms of Use)

Description Matthew Mosesohn 2013-11-14 15:14:00 UTC
Description of problem:
VLAN tagged traffic gets blocked on bnx hardware when using RDO kernel

Version-Release number of selected component (if applicable):
kernel-2.6.32-358.123.2.openstack.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Deploy OpenStack Grizzly (any release) with Neutron + VLAN segmentation
2. Launch two instances within one tenant
3. Try to ping or ssh to your tenant from another

Actual results:
Traffic gets dropped at the driver level and never gets out on the wire

Expected results:
VLAN traffic is routed correctly

Additional info:
VLAN splintering is not preferred because you must create a list of all VLAN IDs in advance for each host.

If you have some advice on how to provide useful debug info while the host is broken, let me know.

Comment 1 Thomas Graf 2013-11-21 01:09:30 UTC
Please confirm whether you are referring to bnx2x or bnx2.

Comment 2 Matthew Mosesohn 2013-11-21 08:12:33 UTC
Thomas, I apologize. We're having difficulty getting access to appropriate physical hardware for reproduction. I need another couple days. Leaving needinfo present.

Comment 3 Thomas Graf 2014-05-12 08:18:38 UTC
This issue has been open for a couple of months with further clarification required from Mirantis. Does this issue still exist and can you provide the required information?

Comment 4 Thomas Graf 2014-05-16 13:27:32 UTC
Closing due to lack of activity.


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