cryptic error when PXE-boot requires an image not yet imported

Bug #1611949 reported by Christian Reis on 2016-08-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Wishlist
Blake Rouse

Bug Description

Today a user on IRC reported an error when trying to enlist a machine; the machine was stuck at the PXELinux boot: prompt. From the screenshot at http://picpaste.com/thumbs/Capture-50dZaauj.1470858075.PNG we noticed the image path contained "no-such-image", and that the machine was detected as i386.

It's not very pleasant that the code that renders the pxelinux template is happy to simply generate no-such-image and move on, as the end-user will really not be able to figure out what needs fixing in order to address the problem.

(This specific context of the error encountered by this IRC user is an autopilot installation on VMWare, and we suspect PXELinux is misdetecting the architecture. But regardless, our failure mode should be better!)

Related branches

Changed in maas:
importance: Undecided → Wishlist
milestone: none → 2.1.0
status: New → Triaged
tags: added: error-surface notifications
Changed in maas:
assignee: nobody → Blake Rouse (blake-rouse)
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers