MAAS 2.0 - CentOS 7 deployment failed

Bug #1627441 reported by ValenBB
54
This bug affects 8 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
High
Unassigned
maas-images
Fix Released
High
Blake Rouse

Bug Description

MAAS version: 2.0.0+bzr5189-0ubuntu1 (16.04.1)

Hardware Brand: HP DL380 Gen9
Storage: RAID0 (2 SSD) and RAID5 (SAS Disks)

Everything from Enlisting to Acquire is successful; however, deploying Centos 7 (provided with MAAS) fails.
Deploying Ubuntu 16.04 is successful.

Error appears after image is transferred:
2016-09-25 05:50:11 (11.0 MB/s) - written to stdout [340058492/340058492]

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.10.0-327.28.3.el7.x86_64
Found initrd image: /boot/initramfs-3.10.0-327.28.3.el7.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-56d65f493d8f854534fe792ecf014b83
Found initrd image: /boot/initramfs-0-rescue-56d65f493d8f854534fe792ecf014b83.img
done
Traceback (most recent call last):
  File "/tmp/tmpl_7qar2l/target/curtin/curtin-hooks.py", line 332, in <module>
    main()
  File "/tmp/tmpl_7qar2l/target/curtin/curtin-hooks.py", line 322, in main
    install_efi(target, uefi_part['device_path'])
  File "/tmp/tmpl_7qar2l/target/curtin/curtin-hooks.py", line 169, in install_efi
    os.path.join(tmp_efi, 'EFI'))
  File "/usr/lib/python3.5/shutil.py", line 303, in copytree
    names = os.listdir(src)
FileNotFoundError: [Errno 2] No such file or directory: '/tmp/tmpl_7qar2l/target/boot/efi/EFI'
Unexpected error while running command.
Command: ['/tmp/tmpl_7qar2l/target/curtin/curtin-hooks']
Exit code: 1
Reason: -
Stdout: ''
Stderr: ''
Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'curthooks']
Exit code: 3
Reason: -
Stdout: b'Generating grub configuration file ...\nFound linux image: /boot/vmlinuz-3.10.0-327.28.3.el7.x86_64\nFound initrd image: /boot/initramfs-3.10.0-327.28.3.el7.x86_64.img\nFound linux image: /boot/vmlinuz-0-rescue-56d65f493d8f854534fe792ecf014b83\nFound initrd image: /boot/initramfs-0-rescue-56d65f493d8f854534fe792ecf014b83.img\ndone\nTraceback (most recent call last):\n File "/tmp/tmpl_7qar2l/target/curtin/curtin-hooks.py", line 332, in <module>\n main()\n File "/tmp/tmpl_7qar2l/target/curtin/curtin-hooks.py", line 322, in main\n install_efi(target, uefi_part[\'device_path\'])\n File "/tmp/tmpl_7qar2l/target/curtin/curtin-hooks.py", line 169, in install_efi\n os.path.join(tmp_efi, \'EFI\'))\n File "/usr/lib/python3.5/shutil.py", line 303, in copytree\n names = os.listdir(src)\nFileNotFoundError: [Errno 2] No such file or directory: \'/tmp/tmpl_7qar2l/target/boot/efi/EFI\'\nUnexpected error while running command.\nCommand: [\'/tmp/tmpl_7qar2l/target/curtin/curtin-hooks\']\nExit code: 1\nReason: -\nStdout: \'\'\nStderr: \'\'\n'
Stderr: ''

Other information:

root@ats-maas01:~# 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.0.0+bzr5189-0ubuntu1~16.04.1 all "Metal as a Service" is a physical cloud and IPAM
ii maas-cli 2.0.0+bzr5189-0ubuntu1~16.04.1 all MAAS client and command-line interface
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 2.0.0+bzr5189-0ubuntu1~16.04.1 all MAAS server common files
ii maas-dhcp 2.0.0+bzr5189-0ubuntu1~16.04.1 all MAAS DHCP server
ii maas-dns 2.0.0+bzr5189-0ubuntu1~16.04.1 all MAAS DNS server
ii maas-proxy 2.0.0+bzr5189-0ubuntu1~16.04.1 all MAAS Caching Proxy
ii maas-rack-controller 2.0.0+bzr5189-0ubuntu1~16.04.1 all Rack Controller for MAAS
ii maas-region-api 2.0.0+bzr5189-0ubuntu1~16.04.1 all Region controller API service for MAAS
ii maas-region-controller 2.0.0+bzr5189-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.0.0+bzr5189-0ubuntu1~16.04.1 all MAAS server Django web framework (Python 3)
ii python3-maas-client 2.0.0+bzr5189-0ubuntu1~16.04.1 all MAAS python API client (Python 3)
ii python3-maas-provisioningserver 2.0.0+bzr5189-0ubuntu1~16.04.1 all MAAS server provisioning libraries (Python 3)

Revision history for this message
ValenBB (valenbb) wrote :
Revision history for this message
ValenBB (valenbb) wrote :

UEFI is enabled and default boot option.
MAAS web interface shows /boot/efi partition after successful commission.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi there,

Seems that the path's are not correct on the curtin hooks. We will need to investigate and try to reproduce on similar hardware.

Changed in maas:
milestone: none → 2.1.0
importance: Undecided → High
status: New → Triaged
Changed in maas:
milestone: 2.1.0 → 2.1.1
Changed in maas:
milestone: 2.1.1 → 2.1.2
Changed in maas:
milestone: 2.1.2 → 2.1.3
Changed in maas-images:
status: New → Triaged
importance: Undecided → High
Changed in maas:
status: Triaged → Invalid
milestone: 2.1.3 → none
Revision history for this message
bryanb229 (bryanb229) wrote :

Any updates, thoughts, comments from anyone on this issue?

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi All,

The issue is when booting UEFI and not with Legacy. We are working on getting a fix for this though. We are targeting this to be fixed by next week.

Thanks!

Revision history for this message
Merlin Hartley (scarabmonkey) wrote :

I can confirm I have exactly the same issue with MAAS Version 2.1.3+bzr5573-0ubuntu1
Switching the box to legacyBIOS is a useful workaround.

Revision history for this message
bryanb229 (bryanb229) wrote :

Checking back to see if there is any update on this bug. I am able to install both Ubuntu 14 & 16 w/ the UEFI option, but neither CentOS 6.6 or 7. If I switch back to BIOS boot mode, it will still work w/ both Ubuntu 14/16 and CentOS 6.6, but not 7. Is anyone else having similar issue?

Revision history for this message
Matt Jarvis (matt-jarvis) wrote :

I have the same problem on an OrangeBox. This is also customer impacting as we have customers wanting to use CentOS on UEFI machines.

Changed in maas-images:
status: Triaged → Fix Committed
Revision history for this message
Shane Peters (shaner) wrote :

Even if the directory structure exists, I'm now seeing the below error when deploying CentOS 7. From what I understand the grub2-efi-modules needs to be installed in the image.

 grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist. Please specify --target or --directory.
 Traceback (most recent call last):
 File "/tmp/tmpecmnmaha/target/curtin/curtin-hooks.py", line 332, in <module>
 main()
 File "/tmp/tmpecmnmaha/target/curtin/curtin-hooks.py", line 322, in main
 install_efi(target, uefi_part['device_path'])
 File "/tmp/tmpecmnmaha/target/curtin/curtin-hooks.py", line 182, in install_efi

Changed in maas-images:
status: Fix Committed → In Progress
assignee: nobody → Blake Rouse (blake-rouse)
Revision history for this message
Andres Rodriguez (andreserl) wrote :

We believe this issue has now been fixed. This is made available in the latest MAAS CentOS 7 images.

Thanks.

Changed in maas-images:
status: In Progress → Fix Released
Revision history for this message
bryanb229 (bryanb229) wrote :

I just tried to do the Centos 7 deployment and it is still hanging on the Web UI. The OS install finishes on the server, but with localhost as the hostname, so this still seems to be an issue.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.