devices web UI is not updating (need to refresh)
Bug #1441159 reported by
Dimiter Naydenov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Blake Rouse |
Bug Description
When I create a device it appears immediately on the Nodes page (in the Devices "tab"). When I update a device (e.g. assign IP or update the hostname) the Devices page is not updated and needs to be reloaded to show the changes.
Using maas 1.8.0~alpha10+
Related branches
lp:~blake-rouse/maas/static-ip-trigger
- Raphaël Badin (community): Approve
-
Diff: 170 lines (+116/-0)3 files modifiedsrc/maasserver/tests/test_triggers.py (+2/-0)
src/maasserver/triggers.py (+42/-0)
src/maasserver/websockets/tests/test_listener.py (+72/-0)
lp:~blake-rouse/maas/dhcp-leases-trigger
- Raphaël Badin (community): Approve
-
Diff: 159 lines (+112/-0)3 files modifiedsrc/maasserver/tests/test_triggers.py (+2/-0)
src/maasserver/triggers.py (+42/-0)
src/maasserver/websockets/tests/test_listener.py (+68/-0)
lp:~blake-rouse/maas/node-results-trigger
- Raphaël Badin (community): Approve
-
Diff: 154 lines (+107/-0)3 files modifiedsrc/maasserver/tests/test_triggers.py (+2/-0)
src/maasserver/triggers.py (+41/-0)
src/maasserver/websockets/tests/test_listener.py (+64/-0)
lp:~blake-rouse/maas/macaddress-triggers
- Gavin Panella (community): Approve
- Ricardo Bánffy (community): Abstain
-
Diff: 254 lines (+207/-0)3 files modifiedsrc/maasserver/tests/test_triggers.py (+3/-0)
src/maasserver/triggers.py (+82/-0)
src/maasserver/websockets/tests/test_listener.py (+122/-0)
Changed in maas: | |
milestone: | none → 1.8.0 |
importance: | Undecided → High |
status: | New → Triaged |
Changed in maas: | |
assignee: | nobody → Blake Rouse (blake-rouse) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Many triggers are missing in the database to update nodes and devices. Updating the node table, event table, and tag link table will cause a node/device update, but other tables still need to be added.
StaticIPAddress
DHCPLease
MACAddress
NodeResult
Also updating a cluster dns name, should trigger and update on all nodes on that cluster. This is not implemented either.