cryptic error when PXE-boot requires an image not yet imported
Bug #1611949 reported by
Christian Reis
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
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://
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
lp:~blake-rouse/maas/fix-1612203-1611949
- Andres Rodriguez (community): Approve
-
Diff: 159 lines (+53/-6)4 files modifiedsrc/maasserver/models/bootresource.py (+5/-5)
src/maasserver/models/tests/test_bootresource.py (+10/-1)
src/maasserver/testing/factory.py (+27/-0)
src/provisioningserver/rackdservices/tftp.py (+11/-0)
| 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.
