UEFi x64 failing to deploy on HP ProLiant DL380 Gen9

This is maas 1.7.5+bzr3369-0ubuntu1~trusty1.

FYI this is a curtin 0.1.0~bzr201-0ubuntu1~14.04.1 install.

Install log shows:

Creating new GPT entries.
The operation has completed successfully.
no partition found /dev/nvme0n11
Could not stat /dev/nvme0n11 --- No such file or directory

The device apparently does not exist; did you specify it correctly?
Unexpected error while running command.
Command: ['mkfs.ext4', '-q', '-L', 'cloudimg-rootfs', '/dev/nvme0n11']
Exit code: 1
Reason: -
Stdout: ''
Stderr: ''

FYI this seems related to
https://bugs.launchpad.net/curtin/+bug/1401190/comments/2 ,
patching curtin with that branch allowed the installation
to make (more) progress, now fails at grub install with:

Setting up grub-efi-amd64-signed (1.34.3+2.02~beta2-9ubuntu1.2) ...
Setting up sbsigntool (0.6-0ubuntu7) ...
Setting up secureboot-db (1.1) ...
Can't access efivars filesystem at /sys/firmware/efi/efivars, aborting
Setting up shim (0.4-0ubuntu4) ...
Setting up shim-signed (1.6+0.4-0ubuntu4) ...
/dev/nvme0n1p15 is not a vfat fs
Unexpected error while running command.
Command: ['install-grub', '--uefi', '/tmp/tmpqQG0b0/target', '/dev/nvme0n1']
Exit code: 1
Reason: -
Stdout: ''
Stderr: ''
Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'curthooks']
Exit code: 3
Reason: -

log: http://paste.ubuntu.com/11550163/

could you give a full log like the partial one you gave above when running current trunk or wily curtin packages?

Unfortunately this deployment had a hard deadline (and
it's already completed), we succeeded using d-i instead
to complete the install to /dev/sda.

FYI I've pasted lshw -class disk -class storage to
http://paste.ubuntu.com/11587331/

AFAICS the bug title should be changed to reflect
curtin and ssd also.

I saw an issue very similar (could well be the same) to this. The host would boot, get an address, report "Fetching Netboot Image" and then fail to retrieve grub.<MAC address> from MAAS. An upgrade to MAAS 1.8 seems to have fixed it.

[Expired for MAAS because there has been no activity for 60 days.]

I have same issue. In my case, MAAS and curtin version is following. I attached maas.log, but I can not see install.log (or curtin.log) under /var/log/maas directory. The target machine was cyclic rebooted. I also attached the SoL output, just removed Serial Number field.

MAAS: "1.8.0+bzr4001-0ubuntu2~trusty1"
Curtin: "0.1.0~bzr221-0ubuntu1~14.04.1"
Hardware: HP ProLiant DL360 Gen9, BIOS Version: P89 v1.40 (05/06/2015)
Boot Mode: UEFI

And the SoL output.

That SoL log doesnt really provide any information. Can you provide a SoL log of the node installing?