Unavailable bootloader needs better error messages

Bug #1714535 reported by David Lawson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Won't Fix
Critical
Unassigned

Bug Description

Attempting to auto-enlist an m400 cartridge results in a PXE boot failure:

Using NIC1 device
TFTP from server 10.189.128.2; our IP address is 10.189.131.5
Filename 'pxelinux.cfg/default-arm-storm'.
Load address: 0x4000800000
Loading: *
TFTP error: '(b'UNHANDLED', 'Unknown Error [spoink:pid=20874:cmd=GetBootConfig:ask=1d0]')' (0)
Starting again

On the MaaS server side, the only error logged is:

2017-09-01 06:27:18 provisioningserver.rackdservices.tftp: [critical] TFTP back-end failed.

Traceback (most recent call last):
Failure: twisted.protocols.amp.UnhandledCommand: (b'UNHANDLED', 'Unknown Error [spoink:pid=31109:cmd=GetBootConfig:ask=e1a]')

Given that this is a pretty straightforward case of not being able to find a bootloader for the appropriate architecture, the log message on the MaaS side could be substantially improved.

Changed in maas:
milestone: none → 2.3.0
importance: Undecided → High
status: New → Triaged
importance: High → Critical
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Ok, so there's actual in the backend that delivers better messages when an image is notresent. The bug here is, however, something that could be causing the message to not be delivered. So I'll make this incomplete until we figure out https://bugs.launchpad.net/maas/+bug/1714533

Changed in maas:
status: Triaged → Incomplete
Changed in maas:
milestone: 2.3.0 → 2.3.x
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Dear user,

This is an automated message.

We believe this bug report is no longer an issue in the latest version of MAAS. For such reason, we are making this issue as Won't Fix. If you believe this issue is still present in the latest version of MAAS, please re-open this bug report.

Changed in maas:
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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