Rackd.log: 2018-03- 01 12:36:42 provisioningser ver.rackdservic es.tftp: pxelinux. Rod said this might be critical, so I'll add it for reference.įrom what I could tell in rackd.log, every EFI boot always comes from a8:1e:84:f2:96:c6 and every BIOS PXE boot comes from a8:1e:84:f2:96:c5. Ii python3- maas-provisioni ngserver 2.3.0-6434- gd354690- 0ubuntu1~ 16.04.1 all MAAS server provisioning libraries (Python 3) Ii python3-django-maas 2.3.0-6434- gd354690- 0ubuntu1~ 16.04.1 all MAAS server Django web framework (Python 3) Un python- maas-provisioni ngserver (no description available)
Un python-maas-client (no description available) Un python-django-maas (no description available) Un maas-region- controller- min (no description available)
Ii maas-region- controller 2.3.0-6434- gd354690- 0ubuntu1~ 16.04.1 all Region Controller for MAAS Ii maas-region-api 2.3.0-6434- gd354690- 0ubuntu1~ 16.04.1 all Region controller API service for MAAS Un maas-cluster- controller (no description available) 04.1 all Ubuntu certification support files for MAAS server Ii maas 2.3.0-6434- gd354690- 0ubuntu1~ 16.04.1 all "Metal as a Service" is a physical cloud and IPAM ||/ Name Version Architecture Description |/ Err?=(none) /Reinst- required (Status,Err: uppercase=bad) | Status= Not/Inst/ Conf-files/ Unpacked/ halF-conf/ Half-inst/ trig-aWait/ Trig-pend Here's the MAAS version information:ĭesired= Unknown/ Install/ Remove/ Purge/Hold I'm attaching the contents of /var/log/maas/* to this bug report. This bug is similar in symptoms to several other "hang-at-grub>" bugs, such as bug #1690878 and bug #1437024 however, I have yet to find a workaround, and this problem occurs 100% of the time. Other systems have commissioned and deployed from this MAAS server both shortly before and after discovering the problem with jehan. Because commissioning sets up partitions, including the critical EFI System Partition (ESP), which are different between BIOS- and EFI-mode boots, I have been unable to test deployment in EFI mode. I've been unable to enlist the node in EFI mode and once enlisted in BIOS mode, commissioning it in EFI mode fails. I've tried dozens of combinations of firmware settings (enabling and disabling various options), with no success the system always seems to fail at the same point. The interaction at the end ("ls" and other commands at the "grub>" prompt) is me trying to identify the GRUB environment these commands were not entered automatically. Minimal BASH-like line editing is supported. This server enlists, commissions, and deploys fine in BIOS/CSM/legacy mode however, in EFI/UEFI mode, it fails, hanging at the "grub>" prompt here's a capture from an IPMI SOL session: Certification recently received a Quanta D52B-1U server (jehan).
0 kommentar(er)
