UI filtering on Workloads does not trigger new websocket requests and does not add checkbox on filter entries
Bug #2023633 reported by
Jacopo Rota
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
Changed in maas-ui: | |
importance: | Undecided → Medium |
milestone: | none → 3.5.0 |
status: | New → Confirmed |
status: | Confirmed → Triaged |
assignee: | nobody → Nick De Villiers (nickdv99) |
To post a comment you must log in.
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) ".