~ltrager/maas:lp1847537_2.6

Last commit made on 2019-11-05
Get this branch:
git clone -b lp1847537_2.6 https://git.launchpad.net/~ltrager/maas
Only Lee Trager can upload to this branch. If you are Lee Trager please log in for upload directions.

Branch merges

Branch information

Name:
lp1847537_2.6
Repository:
lp:~ltrager/maas

Recent commits

4006ff2... by Lee Trager

Backport of ad87cfa LP: #1847537 - Respect the allow_dns field when generating V1 network config.

551e927... by Newell Jensen

backport of 143fce8798a3a7a52f6993d8a200744078b01297

LP: #1847794 - Patch Twisted's FilesystemLock.lock method so that we can handle PermissionError exceptions in the event that the lock file is not deleted.

b600147... by Björn Tillenius

LP #1845351: MAAS sometimes get in a state where machine tags aren't updated from their definitions

Don't use a proxy for the rack-region API communication.

We require the rack to have direct access to the region without going
through a proxy.

Using a proxy for the rack-region communication (HTTP API only) has
partly worked, but been broken.

This fixes the test_check_tag_applied_to_all_machines() failure that
fails intermittently in CI.

(cherry picked from commit 4eee730d67082731ed43fe1075a4ce883fcd3823)

aa81b9b... by Björn Tillenius

LP: #1847046 - MAAS doesn't detect the right PXE interface

Extract the boot interface from the kernel cmdline.

This is more reliable than relying on the PXE boot MAC, since a lot of
cases we don't have it.

There's still code that tries to guess the PXE interface when the
machine boots with UUID, but I change it to keep the current one if it's
on the same VLAN.

(cherry picked from commit 5e371015372acd7f51901235188c74b2e1c25734)

4c5ead5... by Blake Rouse

Fixes LP: #1847086 - Update username max_length to 150 for event model.

Backport of d593bba28ede53bc5215f65df02bbe8f2f72d0e3

8a1ce02... by Björn Tillenius

LP #1845459: Failure creating KVM pod in CI

Re-raise DatabaseErrors if form_pod.save() raises an exception.

The old code tried to mark the node as failed deployment, which failed
since the transaction was broken. Further more, the transaction wouldn't
be retried, which would have make the deploy succeed.

This is a stop-gap fix that improves the situation slightly. It's made
small so tha it can be backported to 2.6. The real fix is to refactor
the processing of the messages, so that marking the node as failed or
succeeded happens in a separate transaction.

(cherry picked from commit 6df0418010f49265549dac05233bc6cdfbc177e0)

cf5dc40... by Kit Randel

* Only display 'show all' if more machines than display limit.
* Increase machine group display limit to 10 machines.

b8bfbd3... by Adam Collard

Release 2.6.1

9c4b2ba... by Adam Collard

2.6.1rc1 changelog

ee83011... by Adam Collard

Add missing changelog for 2.6.1-alpha1