[2.5, UI] Not possible to unset the name of a VLAN

Bug #1802214 reported by Mike Pontillo on 2018-11-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
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.

Tags: ui Edit Tag help
description: updated
Changed in maas:
milestone: 2.5.0rc1 → 2.5.0rc2
Changed in maas:
milestone: 2.5.0rc2 → 2.6.0
Steve Rydz (steverydz) on 2018-12-11
Changed in maas:
assignee: nobody → Steve Rydz (steverydz)
status: Triaged → In Progress
Steve Rydz (steverydz) wrote :

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.

Changed in maas:
assignee: Steve Rydz (steverydz) → Mike Pontillo (mpontillo)
status: In Progress → Triaged
Mike Pontillo (mpontillo) wrote :

I'll see if I can reproduce this in the websocket tests. Thanks for taking a look!

Mike Pontillo (mpontillo) wrote :

I wrote a quick test to confirm this is an issue in the websocket handler (and/or form).

https://paste.ubuntu.com/p/cQzXkTTszW

Given that this is targeted for 2.6.0 and we're trying to get 2.5.1 out at the moment, I'll dig deeper into this on a later date.

Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers