Workload annotation filter includes machines not in acquired or deployed state

Bug #1917376 reported by Bill Wear
6
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: ui
tags: added: ui
Changed in maas-ui:
importance: Undecided → Unknown
Revision history for this message
Caleb Ellis (caleb-ellis) wrote :

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"?

Revision history for this message
Björn Tillenius (bjornt) wrote :

If this is an issue, it's indeed a backend issue. There filtering for workload annotations shouldn't care about machine status, since if the machine isn't deployed, it shouldn't have any workload annotations.

Bill Wear (billwear)
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.
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.