~andreserl/maas:lp1626940_fix_perms_2.3

Last commit made on 2018-05-10
Get this branch:
git clone -b lp1626940_fix_perms_2.3 https://git.launchpad.net/~andreserl/maas
Only Andres Rodriguez can upload to this branch. If you are Andres Rodriguez please log in for upload directions.

Branch merges

Branch information

Name:
lp1626940_fix_perms_2.3
Repository:
lp:~andreserl/maas

Recent commits

3be4619... by Andres Rodriguez

LP: #1626940 - Do not make dhcp config files world readable

ee7ebc1... by Newell Jensen

Backport of 3674eeafd563de2d4688a39b75a26af4ee1d3807

LP: #1760715 -- Fixes how partitions are being updated by calling updateFilesystem instead of updateDisk.

9296353... by Andres Rodriguez

LP: #1513775 - Ensure 'dnssec-validation' gets always parsed

On the original bind config, 'dnssec-validation' is set. In some cases, when parsing the config, 'dnssec-validation' is not removed automatically from the bind's config, but it is always added to MAAS' config. This, sometimes, causes bind to fail to start because of duplicate options.

Backport 947f69e from 'master'

b726d2e... by Lee Trager

Backport of 8005dd8 LP: #1768534 - Fix NTP test when run with chrony or timesyncd

a86a49d... by Lee Trager

Backport of 2c48791 LP: #1768323 - Create generic link for old style hwe kernels.

18b0508 made sure only the ga kernel is launched when the ephemerial
environment is started is a generic kernel by making sure only the 'generic'
hard link is only created for the ga kernel. This did not account for old
style kernels using the format hwe-<first letter of release>. This caused no
generic hard link to be created. Trusty deployments were not effected as MAAS
specifies the real kernel and subarch name(hwe-t). This does not happen with
precise as the commissioning OS is used to deploy and generic is used for the
image subarch instead.

Also fixes a bug where MAAS would use theimage URL for any subarch matching
the arch, osystem, and series. This allows Precise to deploy with current
streams.

18a847c... by Lee Trager

Backport of 69b6984 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.

e999a54... by Andres Rodriguez

LP: #1767137 - Harcode Xenial as the default LTS for 2.3

1663558... by Lee Trager

Backport of cc5216 LP: #1757153 - Fix script runtime while running.

b03e36f... by Newell Jensen

Backport of 0f70f39365701b5c72d136fe46955c779cef351c

LP: #1709482 - Fix partition names on save so that -part# does not keep appending to name.

9699d62... by Andres Rodriguez

LP: #1759284 - Change the interface name gathering during commissioning

The interface names can now be larger than 8 characters before Bionic.
Bionic forward these can be much larger than that. This caused issues
where ifconfig -s would not output the whole interface name. As such,
change the mechanism in which how we discover the interfaces for the DHCP
commissioning script.

Backport: 30729b9dbd4ae82630ea01ee368fcd071c70ac06