| 2016-03-03 21:28:24 |
Blake Rouse |
bug |
|
|
added bug |
| 2016-03-03 21:28:33 |
Blake Rouse |
nominated for series |
|
maas/1.9 |
|
| 2016-03-03 21:28:33 |
Blake Rouse |
bug task added |
|
maas/1.9 |
|
| 2016-03-03 21:28:37 |
Blake Rouse |
maas/1.9: milestone |
|
1.9.2 |
|
| 2016-03-03 21:28:39 |
Blake Rouse |
maas/1.9: status |
New |
Triaged |
|
| 2016-03-03 21:28:41 |
Blake Rouse |
maas/1.9: importance |
Undecided |
High |
|
| 2016-03-03 21:28:45 |
Blake Rouse |
nominated for series |
|
maas/1.10 |
|
| 2016-03-03 21:28:45 |
Blake Rouse |
bug task added |
|
maas/1.10 |
|
| 2016-03-03 21:28:50 |
Blake Rouse |
maas/1.10: status |
New |
Triaged |
|
| 2016-03-03 21:28:51 |
Blake Rouse |
maas/1.10: importance |
Undecided |
High |
|
| 2016-03-03 21:28:53 |
Blake Rouse |
maas/1.10: milestone |
|
1.10.0 |
|
| 2016-03-03 21:29:22 |
Launchpad Janitor |
branch linked |
|
lp:~blake-rouse/maas/force-untagged-api |
|
| 2016-03-04 06:02:00 |
Mike Pontillo |
summary |
API allows attaching physical, bond interface to non untagged VLAN's |
API allows attaching physical, bond interface to VLAN with a known tag |
|
| 2016-03-04 14:03:41 |
Blake Rouse |
summary |
API allows attaching physical, bond interface to VLAN with a known tag |
API allows attaching physical, bond interface to VLAN with a known tag (Inconsistent with UI) |
|
| 2016-03-04 14:06:25 |
Blake Rouse |
description |
The API currently allows administrators to attach a physical or bond interface to a VLAN which is not an untagged vlan on a fabric. This does not match the UI which limits this. Also a VLAN interface can be attached to the untagged VLAN for the fabric. |
The API currently allows administrators to attach a physical or bond interface to a VLAN which is not an untagged vlan on a fabric. This does not match the UI which limits this. Also a VLAN interface can be attached to the untagged VLAN for the fabric.
This is inconsistent with the WebUI. Either MAAS supports placing a physical or bond interface on any VLAN or only the untagged VLAN. We cannot allow the API to do one thing and the UI to do another. It causes confusing for users, its in consistent, and its overall bad UX. Either we support one way or we support the other way, not 50% one way and 50% the other. |
|
| 2016-03-04 20:59:02 |
MAAS Lander |
maas: status |
Triaged |
Fix Committed |
|
| 2016-04-05 14:24:27 |
Blake Rouse |
bug task deleted |
maas/1.10 |
|
|
| 2016-04-05 14:24:32 |
Blake Rouse |
maas: assignee |
|
Blake Rouse (blake-rouse) |
|
| 2016-04-05 14:24:35 |
Blake Rouse |
maas/1.9: assignee |
|
Blake Rouse (blake-rouse) |
|
| 2016-04-05 14:24:37 |
Blake Rouse |
maas/1.9: status |
Triaged |
In Progress |
|
| 2016-04-05 16:01:23 |
Launchpad Janitor |
branch linked |
|
lp:~blake-rouse/maas/fix-1566336-1.9 |
|
| 2016-04-05 16:30:00 |
MAAS Lander |
maas/1.9: status |
In Progress |
Fix Committed |
|
| 2016-04-28 18:46:32 |
Andres Rodriguez |
maas/1.9: status |
Fix Committed |
Fix Released |
|
| 2016-08-18 11:24:33 |
Andres Rodriguez |
maas: status |
Fix Committed |
Fix Released |
|
