Interfaces that have failed tests have confusing status
Bug #1881360 reported by
Lee Trager
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
MAAS | Status tracked in 3.6 | |||||
3.4 |
Won't Fix
|
Low
|
Unassigned | |||
3.5 |
Won't Fix
|
Low
|
Unassigned | |||
3.6 |
Triaged
|
Low
|
Unassigned | |||
maas-ui |
Triaged
|
Low
|
Unassigned |
Bug Description
I ran the internet-
Changed in maas-ui: | |
importance: | Undecided → Unknown |
Changed in maas: | |
milestone: | none → 3.4.0 |
Changed in maas-ui: | |
status: | New → Triaged |
importance: | Unknown → Low |
milestone: | none → 3.4.0 |
Changed in maas: | |
milestone: | 3.4.0 → 3.4.x |
tags: | removed: ui |
Changed in maas: | |
milestone: | 3.4.x → 3.5.x |
Changed in maas-ui: | |
milestone: | 3.4.0 → 3.5.x |
Changed in maas-ui: | |
milestone: | 3.5.x → 3.6.x |
To post a comment you must log in.
The legacy node networking page is by far the most brittle code in maas-ui. I'm marking this as Low mainly because the less we touch that page, the less likely we are to introduce regressions. Plus it's relatively innocuous.
In all likelihood this will only get fixed once node details is rebuilt.