MAAS 2.0 cannot link physical device interfaces to tagged vlans, breaking juju 2.0 multi-NIC containers
Bug #1572070 reported by
Dimiter Naydenov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Blake Rouse | ||
| 1.9 |
Fix Released
|
Critical
|
Blake Rouse | ||
Bug Description
As demonstrated using this script http://
Running the script with 'using_maas_20 = True' gives this output: http://
The error is:
{
"vlan": [
"A physical interface can only belong to an untagged VLAN."
]
}
In contrast, running the same script with 'using_maas_20 = False' (against 1.9.1) we get expected success: http://
This is a regression for Juju 2.0 will prevent the multi-NIC containers provisioning to work on MAAS 2.0.
Related branches
lp:~blake-rouse/maas/fix-1572070
- Andres Rodriguez (community): Approve
-
Diff: 57 lines (+27/-2)2 files modifiedsrc/maasserver/forms_interface.py (+8/-2)
src/maasserver/tests/test_forms_interface.py (+19/-0)
lp:~blake-rouse/maas/fix-1572070-1.9
- Blake Rouse (community): Approve
-
Diff: 49 lines (+26/-2)2 files modifiedsrc/maasserver/forms_interface.py (+7/-2)
src/maasserver/tests/test_forms_interface.py (+19/-0)
| Changed in maas: | |
| status: | New → In Progress |
| importance: | Undecided → Critical |
| assignee: | nobody → Blake Rouse (blake-rouse) |
| milestone: | none → 2.0.0 |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
