I released one of the failing nodes (DL380-G4), ran: maas maas set-config name=curtin_verbose value=true Deployed the node and waited till it failed. Then I ran: maas maaster node get-curtin-config node-1e6e4f34-3e88-11e6-8da5-001a640920e4 and this is the StdOut: robin@IbmRS1:~$ maas maaster node get-curtin-config node-1e6e4f34-3e88-11e6-8da5-001a640920e4 Success. Machine-readable output follows: apt_mirrors: ubuntu_archive: http://archive.ubuntu.com//ubuntu ubuntu_security: http://archive.ubuntu.com//ubuntu apt_proxy: http://192.168.1.150:8000/ debconf_selections: maas: 'cloud-init cloud-init/datasources multiselect MAAS cloud-init cloud-init/maas-metadata-url string http://192.168.1.150/MAAS/metadata/ cloud-init cloud-init/maas-metadata-credentials string oauth_token_key=BW2fFMWap4qWJAvA4w&oauth_token_secret=3xfcj8MAtuSRNhJpntC5w86yww2LVzhb&oauth_consumer_key=vnC7UzTtzRU47BvUFj cloud-init cloud-init/local-cloud-config string apt_preserve_sources_list: true\napt_proxy: http://192.168.1.150:8000/\nmanage_etc_hosts: false\nmanual_cache_clean: true\nreporting:\n maas: {consumer_key: vnC7UzTtzRU47BvUFj, endpoint: ''http://192.168.1.150/MAAS/metadata/status/node-1e6e4f34-3e88-11e6-8da5-001a640920e4'',\n token_key: BW2fFMWap4qWJAvA4w, token_secret: 3xfcj8MAtuSRNhJpntC5w86yww2LVzhb,\n type: webhook}\nsystem_info:\n package_mirrors:\n - arches: [i386, amd64]\n failsafe: {primary: ''http://archive.ubuntu.com/ubuntu'', security: ''http://security.ubuntu.com/ubuntu''}\n search:\n primary: [''http://archive.ubuntu.com/ubuntu'']\n security: [''http://archive.ubuntu.com/ubuntu'']\n - arches: [default]\n failsafe: {primary: ''http://ports.ubuntu.com/ubuntu-ports'', security: ''http://ports.ubuntu.com/ubuntu-ports''}\n search:\n primary: [''http://ports.ubuntu.com/ubuntu-ports'']\n security: [''http://ports.ubuntu.com/ubuntu-ports'']\n ' install: log_file: /tmp/install.log post_files: - /tmp/install.log kernel: mapping: {} package: linux-generic late_commands: maas: - wget - --no-proxy - http://192.168.1.150/MAAS/metadata/latest/by-id/node-1e6e4f34-3e88-11e6-8da5-001a640920e4/ - --post-data - op=netboot_off - -O - /dev/null network: config: - id: eth0 mac_address: 00:14:c2:c1:fe:ad mtu: 1500 name: eth0 subnets: - address: 10.1.1.152/24 dns_nameservers: [] gateway: 10.1.1.100 type: static type: physical - id: eth1 mac_address: 00:14:c2:c1:fe:ac mtu: 1500 name: eth1 subnets: - type: manual type: physical - address: 192.168.1.150 search: - maas type: nameserver version: 1 network_commands: builtin: - curtin - net-meta - custom partitioning_commands: builtin: - curtin - block-meta - custom power_state: mode: reboot reporting: maas: consumer_key: vnC7UzTtzRU47BvUFj endpoint: http://192.168.1.150/MAAS/metadata/status/node-1e6e4f34-3e88-11e6-8da5-001a640920e4 token_key: BW2fFMWap4qWJAvA4w token_secret: 3xfcj8MAtuSRNhJpntC5w86yww2LVzhb type: webhook showtrace: true storage: config: - grub_device: true id: cciss!c0d0 model: LOGICAL VOLUME name: cciss!c0d0 ptable: msdos serial: 600508b1001844395353503958500047 type: disk wipe: superblock - id: cciss!c0d1 model: LOGICAL VOLUME name: cciss!c0d1 serial: 600508b1001844395353503958500048 type: disk wipe: superblock - id: cciss!c0d2 model: LOGICAL VOLUME name: cciss!c0d2 serial: 600508b1001844395353503958500049 type: disk wipe: superblock - id: cciss!c0d3 model: LOGICAL VOLUME name: cciss!c0d3 serial: 600508b100184439535350395850004a type: disk wipe: superblock - device: cciss!c0d0 id: cciss!c0d0-part1 name: cciss!c0d0-part1 number: 1 offset: 4194304B size: 36406558720B type: partition uuid: db74597b-1b1e-432b-ad4f-6df6047f53cb wipe: superblock - fstype: ext4 id: cciss!c0d0-part1_format label: root type: format uuid: f0544d0e-7696-4b88-b0d0-8c7b9857b742 volume: cciss!c0d0-part1 - device: cciss!c0d0-part1_format id: cciss!c0d0-part1_mount path: / type: mount version: 1 verbosity: 3 Next i will try and deploy the failing node with Wily. I appreciate your easy to understand guidance and I am eager to help with this and any other testing.