Activity log for bug #1802214

Date Who What changed Old value New value Message
2018-11-08 01:57:12 Mike Pontillo bug added bug
2018-11-08 01:57:54 Mike Pontillo 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". 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.
2018-11-13 19:03:44 Andres Rodriguez maas: milestone 2.5.0rc1 2.5.0rc2
2018-11-30 18:47:39 Andres Rodriguez maas: milestone 2.5.0rc2 2.6.0
2018-12-11 16:06:21 Steve Rydz maas: assignee Steve Rydz (steverydz)
2018-12-11 16:06:24 Steve Rydz maas: status Triaged In Progress
2018-12-12 14:34:18 Steve Rydz maas: assignee Steve Rydz (steverydz) Mike Pontillo (mpontillo)
2018-12-12 14:34:25 Steve Rydz maas: status In Progress Triaged
2019-09-19 14:49:51 Adam Collard maas: status Triaged Invalid