1.8a9: Deselecting a filter where there are no matching nodes
Bug #1439086 reported by
Adam Collard
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Blake Rouse | ||
Bug Description
I had a bunch of nodes that had failed commissioning, so I filtered by that status, then took a bulk action to power them off (separate bug as to why they're left powered on). I now see my filtered list, they're all in Failed commissioning, power is off. I then bulk commission them.
For some reason (the state changes and no longer matches the filter?) I then see them drop off one by one out of my selected list.
Now I add in the Commissioning filter and see a query of "status:(Failed commissioning,
Related branches
lp:~blake-rouse/maas/fix-multi-bugs-node-listing
- Raphaël Badin (community): Approve
-
Diff: 342 lines (+145/-36)5 files modifiedsrc/maasserver/static/js/angular/controllers/node_details.js (+5/-0)
src/maasserver/static/js/angular/controllers/nodes_list.js (+29/-2)
src/maasserver/static/js/angular/controllers/tests/test_node_details.js (+8/-0)
src/maasserver/static/js/angular/controllers/tests/test_nodes_list.js (+67/-1)
src/maasserver/static/partials/nodes-list.html (+36/-33)
| Changed in maas: | |
| milestone: | none → 1.8.0 |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| summary: |
- Deselecting a filter where there are no matching nodes + 1.8a9: Deselecting a filter where there are no matching nodes |
| tags: | added: ui |
| Changed in maas: | |
| assignee: | nobody → Blake Rouse (blake-rouse) |
| status: | Triaged → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
