Merge ~ltrager/maas:fix_script_result_triggers into maas:master
Proposed by
Lee Trager
Status: | Merged |
---|---|
Approved by: | Lee Trager |
Approved revision: | b7bbb5d9d1bbfb7a3b4a473a4d5849166494a966 |
Merge reported by: | MAAS Lander |
Merged at revision: | not available |
Proposed branch: | ~ltrager/maas:fix_script_result_triggers |
Merge into: | maas:master |
Diff against target: |
264 lines (+57/-162) 4 files modified
src/maasserver/static/js/angular/factories/node_results.js (+11/-25) src/maasserver/static/js/angular/factories/tests/test_node_results.js (+0/-121) src/maasserver/static/js/angular/services/manager.js (+3/-16) src/metadataserver/migrations/builtin/0015_migrate_storage_tests.py (+43/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
MAAS Lander | Needs Fixing | ||
Andres Rodriguez (community) | Approve | ||
Review via email: mp+332946@code.launchpad.net |
Commit message
LP: #1727568, #1727575 - Create migration to show old storage tests on all devices.
MAAS 2.2 did not support assoicated a ScriptResult with a hardware_type or
physical_
these old results should be assoicated with all known PhysicalBlockDe
This was implemented in Javascript but has been causing issues with the
triggers as some ScriptResults are associated with a PhyicalBlockDevice while
others aren't.
Old ScriptResults are now assoicated with the node's known
PhysicalBlockDe
To post a comment you must log in.
lgtm!