Node isn't added to the node listing when it becomes visible
Bug #1447739 reported by
Raphaël Badin
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Blake Rouse | ||
Bug Description
To reproduce:
- one MAAS install with one node deployed
- two clients (non-admins) viewing the node listing page
- the first client, having deployed the node, sees the node 'deployed'
- the second client sees an empty list
- first client releases the node
- first client sees the node 'ready'
- second client still sees an empty list
Expected outcome
- the node should appear on the second client node listing
This is similar to bug 1447736.
Related branches
lp://qastaging/~blake-rouse/maas/fix-notifications-for-node-permissions
- Gavin Panella (community): Approve
- ubuntudotcom1 (community): Approve
-
Diff: 463 lines (+190/-70)5 files modifiedsrc/maasserver/websockets/base.py (+61/-21)
src/maasserver/websockets/handlers/event.py (+6/-4)
src/maasserver/websockets/handlers/tests/test_event.py (+10/-7)
src/maasserver/websockets/protocol.py (+2/-2)
src/maasserver/websockets/tests/test_base.py (+111/-36)
| Changed in maas: | |
| importance: | Medium → High |
| status: | New → In Progress |
| assignee: | nobody → Blake Rouse (blake-rouse) |
| Changed in maas: | |
| importance: | High → Critical |
| milestone: | none → 1.8.0 |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
