[2.5, UI] Not possible to unset the name of a VLAN
Bug #1802214 reported by
Mike Pontillo
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Medium
|
Mike Pontillo | ||
Bug Description
After installing a new MAAS, I noticed that an untagged VLAN MAAS had detected in fabric-1 was actually a tagged VLAN in fabric-0.
I moved the VLAN to the correct fabric, but the VLAN showed up as "100 (Default VLAN)".
I then attempted to delete the VLAN name so it would simply show up as "100", but this caused the VLAN's name to revert to "Default VLAN".
Expected behavior: clearing out the name of the VLAN and then saving it should cause the VLAN's name to be unset.
| description: | updated |
| Changed in maas: | |
| milestone: | 2.5.0rc1 → 2.5.0rc2 |
| Changed in maas: | |
| milestone: | 2.5.0rc2 → 2.6.0 |
| Changed in maas: | |
| assignee: | nobody → Steve Rydz (steverydz) |
| status: | Triaged → In Progress |
Revision history for this message
| Steve Rydz (steverydz) wrote | #1 |
| Changed in maas: | |
| assignee: | Steve Rydz (steverydz) → Mike Pontillo (mpontillo) |
| status: | In Progress → Triaged |
Revision history for this message
| Mike Pontillo (mpontillo) wrote | #2 |
Revision history for this message
| Mike Pontillo (mpontillo) wrote | #3 |
Revision history for this message
| Adam Collard (adam-collard) wrote | #4 |
| Changed in maas: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
It looks like if we save a VLAN with no name, the params we send to the websocket have the name set as an empty string. When the data comes back from the backend, the name is set to what it was previously.