[2.6b6 UI] Adding a fabric with an optional name ends up with a new fabric with automatically assigned name

Bug #1589560 reported by Andres Rodriguez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Blake Rouse

Bug Description

[Description]
While trying to add fabrics on the UI, noticed that fabrics end up having the name automatically assigned by MAAS, rather than the optional name I provided. This doesn't seem to be the case if I add the fabric via the API/CLI.

[Reproduce]
1. Go to networks page.
2. Add a Fabric.
3. Specify an optional name ('optional-fabric')

[Actual Output]
You'll see a fabric is added with name 'fabric-X' instead of the name I specified in the optional name field ('optional-fabric')

[Expected Output]
I expected to see a fabric added with name 'optional-fabric'

Related branches

Changed in maas:
milestone: none → 2.0.0
Changed in maas:
importance: Undecided → Critical
Changed in maas:
status: New → Triaged
assignee: nobody → Blake Rouse (blake-rouse)
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.