Installation failed - /dev/nvme0n11 no such file or directory

[Caroline Edwards]

I have installed MAAS 2.0 beta 5 on a system with Ubuntu 16.04 Server LTS.

maas:
  Installed: 2.0.0~beta5+bzr5026-0ubuntu1~xenial1
  Candidate: 2.0.0~beta5+bzr5026-0ubuntu1~xenial1
  Version table:
 *** 2.0.0~beta5+bzr5026-0ubuntu1~xenial1 500
        500 http://ppa.launchpad.net/maas/next/ubuntu xenial/main amd64 Packages
        500 http://ppa.launchpad.net/maas/next/ubuntu xenial/main i386 Packages
        100 /var/lib/dpkg/status
     2.0.0~beta3+bzr4941-0ubuntu1 500
        500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        500 http://gb.archive.ubuntu.com/ubuntu xenial/main i386 Packages

The cluster is set up with nvme pcie m2 ssds for the bootable disks. The nodes commission successfully but when I deploy them it fails stating:

An error occured handling 'nvme0n1-part1_format': ValueError - '/dev/nvme0n11': no such file or directory
'/dev/nvme0n11': no such file or directory
Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']
Exit code: 3
Reason: -
Stdout: b"An error occured handling 'nvme0n1-part1_format': ValueError - '/dev/nvme0n11': no such file or directory\n'/dev/nvme0n11': no such file or directory\n"
Stderr: ''

However I am able to successfully SSH to the node. It is true that /dev/nvme0n11 does not exist as it is /dev/nvme0n1p1. I believe there was a similar bug in curtin number 1401190 if that helps.

Thanks.

[Andres Rodriguez (andreserl)]

Hi there,

Can you please attach the output of:

maas <user> node get-curtin-config <node's system id>

As well as the full installation log?

[Andres Rodriguez (andreserl)]

Ok, I've talked to the curtin team and this does seem to be an issue with Curtin rather than MAAS. This has already been fixed in curtin trunk and there's a package in xenial-proposed providing the fix.

[Caroline Edwards (caroline-edwards)]

Hi Andres,

Many thanks for your help and I'm very sorry to have created a duplicate
bug.

I'm quite new to all this, are you suggesting I need to update my OS to
xenial-proposed? If so could you please explain how? Or is the
maas/next-proposed what you mean?

Caroline

On 27 May 2016 at 18:04, Andres Rodriguez <email address hidden> wrote:

> *** This bug is a duplicate of bug 1401190 ***
> https://bugs.launchpad.net/bugs/1401190
>
> Ok, I've talked to the curtin team and this does seem to be an issue
> with Curtin rather than MAAS. This has already been fixed in curtin
> trunk and there's a package in xenial-proposed providing the fix.
>
> ** No longer affects: maas
>
> ** This bug has been marked a duplicate of bug 1401190
> curtin makes assumptions about partition names on all devices
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1586464
>
> Title:
> Installation failed - /dev/nvme0n11 no such file or directory
>
> Status in curtin:
> New
>
> Bug description:
> I have installed MAAS 2.0 beta 5 on a system with Ubuntu 16.04 Server
> LTS.
>
> maas:
> Installed: 2.0.0~beta5+bzr5026-0ubuntu1~xenial1
> Candidate: 2.0.0~beta5+bzr5026-0ubuntu1~xenial1
> Version table:
> *** 2.0.0~beta5+bzr5026-0ubuntu1~xenial1 500
> 500 http://ppa.launchpad.net/maas/next/ubuntu xenial/main amd64
> Packages
> 500 http://ppa.launchpad.net/maas/next/ubuntu xenial/main i386
> Packages
> 100 /var/lib/dpkg/status
> 2.0.0~beta3+bzr4941-0ubuntu1 500
> 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64
> Packages
> 500 http://gb.archive.ubuntu.com/ubuntu xenial/main i386
> Packages
>
> The cluster is set up with nvme pcie m2 ssds for the bootable disks.
> The nodes commission successfully but when I deploy them it fails
> stating:
>
> An error occured handling 'nvme0n1-part1_format': ValueError -
> '/dev/nvme0n11': no such file or directory
> '/dev/nvme0n11': no such file or directory
> Installation failed with exception: Unexpected error while running
> command.
> Command: ['curtin', 'block-meta', 'custom']
> Exit code: 3
> Reason: -
> Stdout: b"An error occured handling 'nvme0n1-part1_format': ValueError -
> '/dev/nvme0n11': no such file or directory\n'/dev/nvme0n11': no such file
> or directory\n"
> Stderr: ''
>
> However I am able to successfully SSH to the node. It is true that
> /dev/nvme0n11 does not exist as it is /dev/nvme0n1p1. I believe there
> was a similar bug in curtin number 1401190 if that helps.
>
> Thanks.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1586464/+subscriptions
>

--

[image: Smith Institute Logo]

*Dr Caroline Edwards*
Mathematical Consultant
Smith Institute for Industrial Mathematics and System Engineering
Surrey Technology Centre, Surrey Research Park, Guildford GU2 7YG
Office: 01483-579108 | Mobile: [phone]
www.smithinst.co.uk | Follow @smithinst on twitter
<http://www.twitter.com/smithinst>