UI filtering on Workloads does not trigger new websocket requests and does not add checkbox on filter entries

Bug #2023633 reported by Jacopo Rota
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Committed
Undecided
Unassigned
maas-ui
Fix Committed
Medium
Nick De Villiers
3.4
Fix Committed
Medium
Nick De Villiers

Bug Description

On MAAS 3.4.0~beta2, as per title the filtering on the Workloads does not add checkbox on the entries and does not trigger new websocket requests - the UI does not get updated.

See the video in the attachments

Tags: ui
Revision history for this message
Jacopo Rota (r00ta) wrote :
Changed in maas-ui:
importance: Undecided → Medium
milestone: none → 3.5.0
status: New → Confirmed
status: Confirmed → Triaged
assignee: nobody → Nick De Villiers (nickdv99)
Revision history for this message
Nick De Villiers (nickdv99) wrote :

After some research, it looks like the filter is not being correctly applied in the UI when selected from the dropdown.

As an example, let's take a workload annotation with key "type" and value "production". If you select this in the filter dropdown, the filter gets applied as "workload-type:production:()". This is not valid and will not match anything. Instead, it should be applied as "workload-type:(=production)".

Changed in maas-ui:
status: Triaged → In Progress
Revision history for this message
Adam Collard (adam-collard) wrote :
Revision history for this message
Nick De Villiers (nickdv99) wrote :
Changed in maas-ui:
status: In Progress → Fix Committed
Revision history for this message
Nick De Villiers (nickdv99) wrote :
Changed in maas:
status: New → Fix Committed
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.