[Bug 1665143] [NEW] Commission scripts select the wrong nvme device link, then fails to report any storage

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The udev package provides /lib/udev/rules.d/60-persistent-storage.rules
which creates two symlinks for nvme devices, under /dev/disk/by-id/. The
first link name includes the device wwid and the second includes the
device model/serial. The commission script selects the first link
discovered and subsequently attempts to store it in a FilePath field,
which allows for 100 characters. Since the wwid link is greater than 100
characters an exception is thrown, causing not only the nvme device not
to be registered but all other storage devices as well. Although
commissioning completes there is no storage assigned, which makes
deployment of the node impossible.

This issue has blocked all test runs performed by the CDO-QA test
infrastructure, since every run installs MAAS on a fresh machine and
commissions new nodes. The failure is seen when installing from either
ppa:maas/next (2.2.0~beta2) or ppa:maas/stable (2.1.3+bzr5573).

ubuntu at meowth:~$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                            Version                              Architecture Description
+++-===============================-====================================-============-=================================================
ii  maas                            2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all          "Metal as a Service" is a physical cloud and IPAM
ii  maas-cli                        2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all          MAAS client and command-line interface
un  maas-cluster-controller         <none>                               <none>       (no description available)
ii  maas-common                     2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all          MAAS server common files
ii  maas-dhcp                       2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all          MAAS DHCP server
ii  maas-dns                        2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all          MAAS DNS server
ii  maas-proxy                      2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all          MAAS Caching Proxy
ii  maas-rack-controller            2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all          Rack Controller for MAAS
ii  maas-region-api                 2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all          Region controller API service for MAAS
ii  maas-region-controller          2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all          Region Controller for MAAS
un  maas-region-controller-min      <none>                               <none>       (no description available)
un  python-django-maas              <none>                               <none>       (no description available)
un  python-maas-client              <none>                               <none>       (no description available)
un  python-maas-provisioningserver  <none>                               <none>       (no description available)
ii  python3-django-maas             2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all          MAAS server Django web framework (Python 3)
ii  python3-maas-client             2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all          MAAS python API client (Python 3)
ii  python3-maas-provisioningserver 2.2.0~beta2+bzr5717-0ubuntu1~16.04.1 all          MAAS server provisioning libraries (Python 3)

After re-commissioning one of the servers with ssh enabled the attached
log files were collected. Please note that from the shell it can be seen
that block devices are discovered and even the commissioning output
found in /tmp/user_data.sh.IK9yVp/out/00-maas-07-block-devices lists
devices (see attached), where-as this file is shown as a 0 byte file
from the GUI (see screen shot).

There are 'HTTP Error 500: INTERNAL SERVER ERROR' errors in cloud-init-
output.log

ubuntu at azurill:~$ uname -a
Linux azurill 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:55:08 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

ubuntu at azurill:~$ sudo lsblk  --exclude 1,2,7 -d -P -o NAME,RO,RM,MODEL,ROTA
NAME="sdb" RO="0" RM="0" MODEL="LOGICAL VOLUME  " ROTA="1"
NAME="sdc" RO="1" RM="0" MODEL="VIRTUAL-DISK    " ROTA="1"
NAME="sda" RO="0" RM="0" MODEL="LOGICAL VOLUME  " ROTA="1"
NAME="nvme0n1" RO="0" RM="0" MODEL="INTEL SSDPEDME400G4

** Affects: maas
     Importance: High
         Status: Fix Released

** Affects: maas/2.1
     Importance: High
     Assignee: Andres Rodriguez (andreserl)
         Status: Fix Released

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: Confirmed


** Tags: cdo-qa sts
-- 
Commission scripts select the wrong nvme device link, then fails to report any storage
https://bugs.launchpad.net/bugs/1665143
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to systemd in Ubuntu.