~bjornt/maas:bug-1727962-device-handler-expected-queries

Last commit made on 2017-10-30
Get this branch:
git clone -b bug-1727962-device-handler-expected-queries https://git.launchpad.net/~bjornt/maas
Only Björn Tillenius can upload to this branch. If you are Björn Tillenius please log in for upload directions.

Branch merges

Branch information

Name:
bug-1727962-device-handler-expected-queries
Repository:
lp:~bjornt/maas

Recent commits

b2d98b9... by Björn Tillenius

Fix lint.

1cf3d39... by Björn Tillenius

Merge branch 'master' into bug-1727962-device-handler-expected-queries

03ca7f4... by Andres Rodriguez

Update debian/change & CHANGELOG

98b2905... by Blake Rouse

Recreate RPC connection in the database when updating the running regiond processes.

baf9ba9... by Lee Trager

LP: #1726534 - Fio sometimes contains a '.' in its output

03f6d69... by Newell Jensen

LP: #1727547 -- Modifies the node model signals so that FAILED_TESTING is no longer blacklisted from updating the node's previous status.

This is needed so that we can actually go back to a FAILED_TESTING state when aborting tests. Additionally, FAILED_TESTING is added to the NODE_TESTING_RESET_READY_TRANSITIONS so that in the event that the previous node status was FAILED_TESTING, that upon successful completion of running tests, it will go to the READY state.

5b6d594... by Lee Trager

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_blockdevice. When the UI was updated in 2.3 it was decided that
these old results should be assoicated with all known PhysicalBlockDevices.
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
PhysicalBlockDevices in a migration so the UI gets a similar data set.

e2fe293... by Lee Trager

LP: #1721824, #1721823 - Add health status

The UI now shows the health status of the node when the spinner isn't being
shown. The health status is the overall status of all commissioning and
testing scripts. Like the health status icons for CPU, memory, and storage
the health status icon will only display if there is a problem.

The commissioning, testing, CPU, memory, storage, and overall health are now
reported on the API. Like the websocket ScriptResults are cached so they are
only loaded once.

04933ea... by Björn Tillenius

LP: #1722406 - API allows deploying a machine that's already deployed

Now the API only allows deploying a node that is in READY or ALLOCATED,
just like the UI works.

82f3652... by Alberto Donato

Fix flaky test in TestFindingAndDismissingNotifications.