[1.9] Failed to deploy Ubuntu on IBM x3850 via MAAS v1.9.0

[Joey Li]

The IBM x3850 cannot be deployed by MAAS after upgrade it to v1.9.0. In previous version, v1.8.3, it could be deployed.

Follows are re-create steps :
1. Add node to MAAS. Successful.
2. Commission it. Successful.
3. Deploy it.
3.1 It booted via PXE, and the OS has been installed later. Successful.
3.2 It rebooted and try to start from local disk. Failed.

From the console, it's tried to boot the OS from a file which doesn't exist.
In error message, it's tried to boot from /ACPI(a0341d0,0)/PCI(0,3)/PCI(0,0)/Ctrl(0)/SCSI(0,0)/HD(1,800,100000,5079aa04f422334d,2,2)/File(\efi\ubuntu)/File(shimx64.efi)

But in the firmware setup page, the boot place is PCIRoot(0x0)/Pci(0x3,0x0)/Pci(0x0,0x0)/Ctrl(0x0)/Scsi(0x0,0x0)/HD(1,GPT,04AA7950-22F4-4D33-90FD-DC3B8FF353D9,0x800,0x100000)

Maas point to a place where doesn't contain the boot file.

It can be booted successfully after change the boot file manually.

openstack@MAAS:~$ 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 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.0+bzr4533-0ubuntu1~trusty1 all MAAS server provisioning libraries

[Joey Li (joey-li)]

Add during the deploy phase, it keep report file descriptor leaked messages.

Error: /dev/sda: unrecognised disk label
mdadm: No arrays found in config file or automatically
Creating new GPT entries.
The operation has completed successfully.
Error: /dev/sdb: unrecognised disk label
mdadm: No arrays found in config file or automatically
Error: /dev/sdb: unrecognised disk label
The operation has completed successfully.
The operation has completed successfully.
File descriptor 3 (socket:[14934]) leaked on vgcreate invocation. Parent PID 11766: python
File descriptor 4 (/curtin/configs/config-000.cfg) leaked on vgcreate invocation. Parent PID 11766: python
File descriptor 5 (/curtin/configs/config-001.cfg) leaked on vgcreate invocation. Parent PID 11766: python
File descriptor 6 (/curtin/configs/config-002.cfg) leaked on vgcreate invocation. Parent PID 11766: python
File descriptor 7 (/curtin/configs/config-003.cfg) leaked on vgcreate invocation. Parent PID 11766: python
File descriptor 8 (/curtin/configs/config-004.cfg) leaked on vgcreate invocation. Parent PID 11766: python
File descriptor 10 (/tmp/install.log) leaked on vgcreate invocation. Parent PID 11766: python
File descriptor 11 (/tmp/install.log) leaked on vgcreate invocation. Parent PID 11766: python
  No physical volume label read from /dev/sda2
  Physical volume "/dev/sda2" successfully created
  Volume group "vgroot" successfully created
File descriptor 3 (socket:[14934]) leaked on lvcreate invocation. Parent PID 11766: python
File descriptor 4 (/curtin/configs/config-000.cfg) leaked on lvcreate invocation. Parent PID 11766: python
File descriptor 5 (/curtin/configs/config-001.cfg) leaked on lvcreate invocation. Parent PID 11766: python
File descriptor 6 (/curtin/configs/config-002.cfg) leaked on lvcreate invocation. Parent PID 11766: python
File descriptor 7 (/curtin/configs/config-003.cfg) leaked on lvcreate invocation. Parent PID 11766: python
File descriptor 8 (/curtin/configs/config-004.cfg) leaked on lvcreate invocation. Parent PID 11766: python
File descriptor 10 (/tmp/install.log) leaked on lvcreate invocation. Parent PID 11766: python
File descriptor 11 (/tmp/install.log) leaked on lvcreate invocation. Parent PID 11766: python
  Logical volume "lvroot" created
Error: /dev/dm-0: unrecognised disk label
mkfs.fat: warning - lowercase labels might not work properly with DOS or Windows
mkfs.fat 3.0.26 (2014-03-07)
Error: /dev/dm-0: unrecognised disk label
--2016-02-15 05:50:02-- http://192.168.1.2:5248/images/ubuntu/amd64/generic/trusty/release/root-tgz
Connecting to 192.168.1.2:5248... connected.
HTTP request sent, awaiting response... 200 OK
Length: 328093608 (313M) [text/html]
Saving to: 'STDOUT'

     0K ........ ........ ........ ........ ........ ........ 0% 23.6M 13s
  3072K ........ ........ ........ ........ ........ ........ 1% 32.2M 11s
  6144K ........ ........ ........ ........ ........ ........ 2% 30.9M 11s
  9216K ........ ........ ........ ........ ........ ........ 3% 31.8M 10s
 12288K ........ ........ ........ ........ ........ ........ 4% 32.3M 10s
 15360K ........ ........ ........ ........ ........ ........ 5% 33.0M 10s
 18432K ........ ........ .......

[Andres Rodriguez (andreserl)]

Hi Joey,

Can you please do the following:

1. re-commission the machine, try to re-deploy and see if the issue still persists.
2. Get the curtin config: maas <user> node get-curtin-config <systemd_id>
3. Check the version of curtin you are running: dpkg -l | grep curtin

Thanks.

[Joey Li (joey-li)]

Hi Andres,
Thanks for your advises!
1. I tried that, but it doesn't help. I also tried delete the machine from MAAS, add it back and commission it again. When it rebooted after PXE boot, it still cannot find the correct file to boot from.

2. Please find it in follows attachments.

3. openstack@MAAS:~$ dpkg -l | grep curtin
ii curtin-common 0.1.0~bzr314-0ubuntu1 all Library and tools for curtin installer
ii python-curtin 0.1.0~bzr314-0ubuntu1 all Library and tools for curtin installer

[Ryan Harper (raharper)]

Hi,

Can you attach the complete curtin deploy log? The attached log starts part of the way through.

[Launchpad Janitor (janitor)]

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