MAAS

~deadlight/maas:1769099-double-deploy

  1. Git
  2. lp:~deadlight/maas
  3. 1769099-double-deploy
Last commit made on 2018-05-04
Get this branch:
git clone -b 1769099-double-deploy 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:
1769099-double-deploy
Repository:
lp:~deadlight/maas

Recent commits

42feaf3... by Karl Williams

LP: #1769099 - remove duplicate markup (artefact of bad merge?)

2abc01f... by Newell Jensen

LP: #1764560 -- Only allow admin users to be able to add a Pod.

9994a48... by Björn Tillenius

LP: #1764561 - Non admins are presented with the 'add machine/add chassis' forms

6b1faca... by Alberto Donato

fix flaky websocket test

fef4e5b... by Alberto Donato

LP: #1768796 - add missing python3-macaroonbakery dependency for python3-maas-client

6236998... by Anthony Dillon

LP: #1764784 - Remove the nested scrollbars in the suggestion list

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.