MAAS

~deadlight/maas:action-notifications

  1. Git
  2. lp:~deadlight/maas
  3. action-notifications
Last commit made on 2018-05-03
Get this branch:
git clone -b action-notifications https://git.launchpad.net/~deadlight/maas
Only Karl Williams can upload to this branch. If you are Karl Williams please log in for upload directions.

Branch merges

Branch information

Name:
action-notifications
Repository:
lp:~deadlight/maas

Recent commits

bc1c6b7... by Karl Williams

LP: #1763835 - Revert action notifications on the machine listing to plain text with icons

9dbfad5... by Andres Rodriguez

debiab/changelog: Update to match release & open 2.4.0~rc1

62682ab... by Andres Rodriguez

LP: #1768321 - Fix regression and really fix LP: #1730525

This branch correctly uses the deployed os/release/kernel for DISK_ERASING or ENTERING_RESCUE_MODE machines on Deployed nodes, and fixes the regressions introduced by LP: #1730525. Also ensures the commissioning os/kernel is used when performing hardware testing on deployed machines.

5b47240... by Newell Jensen

Add owner and hostname properties on Event model. Update events API endpoint to filter on username or user.username when owner is passed to the events query.

69b6984... by Lee Trager

LP:1701352 - Set default exit status to 1 when failure.

When Curtin sends the metadata server the installation result does not
include an exit status. It indicates pass or failure with SUCCESS or
FAILURE as the result. When storing the result if no exit status was given
MAAS assumed the script passed and set the exit status to 0. This caused
the ScriptResult for the installation log in both the UI and API to always
be passed even when Curtin failed and the node is marked failed deployment.
Now when Curtin sends failure 1 is set causing the ScriptResult for the
installation log to be set to FAILED. Commissioning and testing results use
a different API end point and are uneffected by this change.

f5aa243... by Blake Rouse

Use log.debug instead of maaslog.debug so all debug messages go to regiond.log and rackd.log when debug is enabled.

afabf63... by Karl Williams

LP: #1766651 - Test actions markup restructure

5ffec9e... by Anthony Dillon

Improve the controller options header

dd7cf0e... by Lee Trager

LP: #1766370 - Check if boot sources have changed before completing an import.

0e8a9bc... by Blake Rouse

Add ability to enable debug on rackd. Set all loggers to DEBUG for both regiond and rackd in debug mode. Don't use Django debug cursor in debug mode unless in dev environment, so good performance and no memory leaks when running installed in debug mode. Log all RPC sent and received messages when in debug mode.