Bug #2762
Automatic Bridge naming may lead to unusable networks
| Status: | Closed | Start date: | 02/27/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 4.6 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.0 |
Description
OpenNebula automatically generates bridge names based on the vnetid. If the bridge is to be used with a vlanid, it should use the same name whenever the VLANID is the same. Conflicting situations are:
- Delete and create a vnet with the same vlanid
- Multiple vnets using the same vlanid
Associated revisions
bug #2762: Generate BRIDGE as "onebr<vlanid>" if vlan_id is defined
(cherry picked from commit d1ea5db93c2683727f408d920bdae9c95308ef47)
bug #2762: Generate BRIDGE as "onebr<vlanid>" if vlan_id is defined
(cherry picked from commit d1ea5db93c2683727f408d920bdae9c95308ef47)
bug #2762: Prevent collitions between vlanid and vnetid
(cherry picked from commit ad1276927c8d6089f240a7bd8cf43f4ae7e57d96)
bug #2762: Prevent collitions between vlanid and vnetid
(cherry picked from commit ad1276927c8d6089f240a7bd8cf43f4ae7e57d96)
History
#1
Updated by Ruben S. Montero over 7 years ago
- Status changed from New to Closed
- Resolution set to fixed