Wrong OVS flows created for new networks
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
YAMAMOTO Takashi |
Bug Description
neutron-
Restarting the neutron-
The issue has been observed using VLAN as a network_type and no other special configurations (like DVR being enabled), while running tempest tests: tempest.
For example, testr run tempest.
Hypervisor used: Hyper-V. The port on Hyper-V are properly bound and the VLAN tag properly set, the ports are marked as "alive". The network traffic arrives with the proper VLAN tag at the Networking Controller. The bug is unrelated to neutron-
This issue has been observed in the Liberty release.
Details: http://
IRC discussion: http://
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in neutron: | |
importance: | Undecided → High |
tags: | removed: liberty-backport-potential |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
For a brief summary. The local VLAN mapping between a network VLAN and the br-int tag seems to be getting mangled. Somehow two tags become associated with one real external network. This leads to incorrect rewrite rules for the devices on the other tag.