Local booting a node uses PXE's unreliable LOCALBOOT

Bug #1034198 reported by Julian Edwards
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Critical
Julian Edwards

Bug Description

Instead it should use chain.c32. The PXE config should be:

DEFAULT local
PROMPT 0
TIMEOUT 0
TOTALTIMEOUT 0
ONTIMEOUT local

LABEL local
        KERNEL chain.c32

It also means we need to put chain.c32 in the appropriate places in the tftp tree (where TFTP is rooted for amd64 and i386).

Related branches

Changed in maas:
status: New → Triaged
importance: Undecided → Critical
Revision history for this message
Robie Basak (racb) wrote :

Note that it should use chain.c32 on Intel only. On all other architectures, please continue using LOCALBOOT.

(I understand that you may decide to switch completely to chain.c32 for now and rely on an external ARM patch for ARM people, which is fine, and I'll track that)

Revision history for this message
Julian Edwards (julian-edwards) wrote : Re: [Bug 1034198] Re: Local booting a node uses PXE's unreliable LOCALBOOT

On Wednesday 08 August 2012 12:51:07 you wrote:
> Note that it should use chain.c32 on Intel only. On all other
> architectures, please continue using LOCALBOOT.
>
> (I understand that you may decide to switch completely to chain.c32 for
> now and rely on an external ARM patch for ARM people, which is fine, and
> I'll track that)

The configs are rendered on the fly in the custom TFTP server, so serving up a
special one for ARM is pretty easy.

Changed in maas:
status: Triaged → In Progress
assignee: nobody → Julian Edwards (julian-edwards)
Changed in maas:
status: In Progress → Fix Released
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.