[l23 network][network_template] vlan_ids of add-patch method in transformation gets omitted if a tuple of bridges is hybrid
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Confirmed
|
Medium
|
Sergey Vasilenko | ||
| Mitaka |
Confirmed
|
Medium
|
Sergey Vasilenko | ||
Bug Description
Detailed bug description:
vlan_ids of add-patch method in transformation gets omitted silently if a tuple of bridges is hybrid
I'd suggest either fail or create a big warning
Steps to reproduce:
Create a env
Devise a network template where there is a add-patch method between `lax` and `ovs` bridges (or vice versa) and vlan_ids option set to non [0,0] value
Upload the network template
Deploy the env
Expected results:
OVS patch is created and vlan_id is present (can be verified by `ovs-vsctl show`)
Actual result:
OVS patch is created but unfortunately vlan_id is absent (can be verified by `ovs-vsctl show`)
Reproducibility:
Always
Workaround:
Create sub-interface where VLAN tag cutting down and connect this sub-interface by OVS patch
Impact:
Some schemas can't be deployed
Description of the environment:
Operation system: Ubuntu
Versions of components: Fuel 8.0+
| Changed in fuel: | |
| assignee: | nobody → l23network (l23network) |
| milestone: | none → 10.0 |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| Roman Sokolkov (rsokolkov) wrote | #1 |
| summary: |
[l23 network][network_template] vlan_ids of add-patch method in - transformation gets omitted if tuple of bridges is hybrid + transformation gets omitted if a tuple of bridges is hybrid |
| tags: | added: customer-found |
| Changed in fuel: | |
| assignee: | Registry Administrators (registry) → Sergey Vasilenko (xenolog) |
| Changed in fuel: | |
| milestone: | 10.0 → 10.1 |
Please increase bug importance as we have potential customer for this use case.