Workload annotation filter includes machines not in acquired or deployed state
Bug #1917376 reported by
Bill Wear
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Undecided
|
Unassigned | ||
| maas-ui |
Fix Released
|
Unknown
|
|||
Bug Description
On bolla, when selecting "Workload" from the Filter dropdown, the machine count for each existing key=value owner_data pair counts machines which are not in the "Acquired" or "Deployed" state. Upon selecting one of those existing key=value pairs, machines can be show which are not in the "Acquired" or "Deployed" state.
| tags: | added: ui |
| Changed in maas-ui: | |
| importance: | Undecided → Unknown |
Revision history for this message
| Caleb Ellis (caleb-ellis) wrote | #1 |
Revision history for this message
| Björn Tillenius (bjornt) wrote | #2 |
| Changed in maas: | |
| status: | New → Triaged |
| Changed in maas-ui: | |
| status: | New → Fix Released |
| Changed in maas: | |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| milestone: | none → 3.2.0-beta1 |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I can fix this on the UI side, but isn't this a backend bug? Shouldn't it be impossible to set workload annotations on a machine that is neither "Acquired" nor "Deployed"?