Created by Andres Rodriguez and last modified
Get this branch:
bzr branch lp:~andreserl/maas/lp1665143
Only Andres Rodriguez can upload to this branch. If you are Andres Rodriguez please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Andres Rodriguez

Recent revisions

5758. By Andres Rodriguez

Make updates

5757. By Andres Rodriguez

Make updates

5756. By Andres Rodriguez

Work around issue when discovering nvme

5755. By Andres Rodriguez

[r=andreserl,mpontillo][bug=][author=andreserl] Ensure that we can discover a wedge BMC even if we detect a connected 'ipmi' device

5754. By Gavin Panella

[r=blake-rouse][bug=][author=allenap] Concurrent calls to getClientNow will not cause an update storm.

5753. By Newell Jensen

[r=lamont][bug=1665839][author=newell-jensen] Sieve the newly composed machine based off of node_id.

5752. By Gavin Panella

[r=allenap][bug=][author=allenap] Add to the list of development packages needed for Yakkety and Zesty.

5751. By Gavin Panella

[r=andreserl][bug=][author=allenap] Use the new styling for notifications in the UI and group by category.

5750. By Blake Rouse

[r=newell-jensen][bug=1664732][author=blake-rouse] Fix pod deletion to only decompose machines that MAAS has composed. Convert pod deletion into an async operation.

MAAS know records the creation type of a machine. This type allows MAAS to know what to do upon deletion of that machine. If the machine existed in the pod or was added to the pod out of band from MAAS then it will not be decomposed when the machine or pod is deleted. If the machine was created by MAAS then it will be decomposed in the pod when the machine or pod is deleted. The pod delete operation is not an asynchronous operation where it tries its best to decompose all machines. If decomposing fails then the deletion process will be stopped and the reason for the failure will be raised. If all the machines that required decomposition are successfully decomposed then it will also delete the pre-existing machines and the pod.

5749. By Lee Trager

[r=brendan-donegan,mpontillo][bug=][author=ltrager] Fix smartctl test when running on hardware RAID and unsupported hardware.

The smartctl --scan command lists all drives on the system along with the
device type and any options needed to run smartctl against the drive. While the extra options aren't needed for a typical SCSI drive, they are needed when running smartctl on certain hardware RAID systems to indicate which drive is to be tested.

smartctl --scan also lists all drives it can find, it does not filter out
drives which do not support SMART. The script now verifies all drives support SMART before scanning.

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
This branch contains Public information 
Everyone can see this information.