Node passes commissioning without any disks

[Jason Hobbs]

This is with MAAS 1.7.1~rc1+bzr3322-0ubuntu1~trusty1.

This node reports storage size 1 in the UI, but has no disks attached Here is the LSHW XML:
http://paste.ubuntu.com/9481485/

This node is now in the 'Ready' pool but it isn't really usable because it doesn't have any disks. MAAS doesn't tell me that is has no disks - I just noticed the storage size looked off. I would prefer the disk not go to 'Ready' state if it's not ready to use.

[Christian Reis (kiko)]

Note that according to bug 1402280 that lshw can't be fully trusted anyway, so this may require deeper changes in order to be fully fixed.

[Christian Reis (kiko)]

I just ran into this myself when trying to install on a node which I discovered had no disk. Strangely, it reported having 1 GB of disk after commissioning, and I got a strange curtin error in the install log; I'll attach the screenshots that show this off.

[Ken D'Ambrosio (ken-jots)]

Yeah -- same here. Of my 15 hosts, 13 of them show 1 GB disks. I'm assuming it's somehow trying to provision with the ISO it PXE booted with (as opposed to the 1 TB disk that all nodes are provisioned with, and the other two found correctly) :

        - lshw:node:
            id: disk
            claimed: true
            class: volume
            handle: SCSI:06:00:00:01
            - lshw:description:
              EXT4 volume
            - lshw:product:
              VIRTUAL-DISK
            - lshw:vendor:
              Linux
            - lshw:physid:
              0.0.1
            - lshw:businfo:
              scsi@6:0.0.1
            - lshw:logicalname:
              /dev/sdb
            - lshw:logicalname:
              /media/root-ro
            - lshw:dev:
              8:16
            - lshw:version:
              1.0
            - lshw:serial:
              ce62663c-1fb4-4b14-bce5-39a359af779d
            - lshw:size:
              units: bytes
              1476395008

[Ken D'Ambrosio (ken-jots)]

Looks like this is directly related to, but not quite a duplicate of, this: https://bugs.launchpad.net/maas/+bug/1318382

[Jason Hobbs (jason-hobbs)]

What version of MAAS are you running Ken?

1.7 has much better disk identification than 1.5 does and will likely fix
the issues you're seeing with incorrect disk detection. You can pick it up
from the maas-maintainers/stable

ppa: https://launchpad.net/~maas-maintainers/+archive/ubuntu/stable

On Fri, Apr 10, 2015 at 11:57 AM, Ken D'Ambrosio <email address hidden> wrote:

> Looks like this is directly related to, but not quite a duplicate of,
> this: https://bugs.launchpad.net/maas/+bug/1318382
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1401703
>
> Title:
> Node passes commissioning without any disks
>
> Status in MAAS:
> Triaged
>
> Bug description:
> This is with MAAS 1.7.1~rc1+bzr3322-0ubuntu1~trusty1.
>
> This node reports storage size 1 in the UI, but has no disks attached
> Here is the LSHW XML:
> http://paste.ubuntu.com/9481485/
>
> This node is now in the 'Ready' pool but it isn't really usable
> because it doesn't have any disks. MAAS doesn't tell me that is has no
> disks - I just noticed the storage size looked off. I would prefer the
> disk not go to 'Ready' state if it's not ready to use.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1401703/+subscriptions
>

[Ken D'Ambrosio (ken-jots)]

Sorry -- should have said. Using 1.7.2 from the PPA.

[Jason Hobbs (jason-hobbs)]

On 04/10/2015 02:36 PM, Ken D'Ambrosio wrote:
> Sorry -- should have said. Using 1.7.2 from the PPA.

Thanks - could you file a new bug about the 1GB disk identification
behaviour you're seeing?

Thanks,
Jason

[Christian Reis (kiko)]

Note that for diskless node support we probably wouldn't want this to be fatal.

[Andres Rodriguez (andreserl)]

Hi!

**This is an automated message**

We believe this is may no longer be an issue in the latest MAAS release. Due to the date of this bug report, we are marking this bug report as invalid. If you believe this is still an issue, please re-open this bug report.

Thanks