New interface hashing breaks upgrades for LinuxBridge
Bug #1504647 reported by
Sean M. Collins
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Sean M. Collins |
Bug Description
Code introduced in https:/
IRC conversation:
This bug is to fix upgrade, not fix the naming scheme.
tags: | added: linuxbridge |
Changed in neutron: | |
importance: | Undecided → High |
status: | New → Confirmed |
milestone: | none → mitaka-1 |
Changed in neutron: | |
assignee: | nobody → dql (duquanglong) |
Changed in neutron: | |
assignee: | dql (duquanglong) → nobody |
Changed in neutron: | |
assignee: | nobody → dql (duquanglong) |
Changed in neutron: | |
assignee: | dql (duquanglong) → nobody |
summary: |
- Ensure new interface hashing does not break upgrades + New interface hashing breaks upgrades for LinuxBridge |
description: | updated |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The old algorithm doesn't hash interface names so it fails to generate valid interface names when:
# len('%s.%s' % (physical_interface + vlan)) > 15 interface) > 14 - len(vlan)
len(physical_
The new algorithm hashs interface names (and generate different names) when:
# large_vlan is a 4 digit vlan /review. openstack. org/#/c/ 224064/ 8/neutron/ tests/unit/ plugins/ common/ test_utils. py interface) > 10
# len('%s.%s' % (physical_interface + large_vlan)) > 15
# it's sadly not highlighted in https:/
len(physical_
It means that old/new algorithms generate valid but different interface names when:
10 < len(physical_ interface) <= 14 - len(vlan) # implies vlan < 1000
So they behave differently when old algorithm generate valid names only for a subset of all vlans