Unable to pxeboot machines (2.6.0-7802 and 2.8.2-8577)
Bug #1836089 reported by
Phil Merricks
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Expired
|
High
|
Unassigned |
Bug Description
I am unable to boot machines in 2.6.0-7802 that I was previously able to pxeboot - verified by pxeboot attempt using 2.4.2-7034. This is a serious regression for me and prevents buildout of my environment, as it depends on Virsh Pod deployment during commission/deploy.
Added some info in the comment below for output. Note my testing is with 2 LXD deployed MAAS (all config) containers, 1 of each version.
description: | updated |
Changed in maas: | |
status: | Confirmed → Invalid |
status: | Invalid → Triaged |
importance: | Undecided → High |
Changed in maas: | |
status: | Incomplete → New |
status: | New → Incomplete |
To post a comment you must log in.
On IRC Roaksoax suggested this may be due to an issue in Syslinux. I'm not easily able to determine the version of Syslinux my MAAS installs are using. But assuming they're using the version that is installed by syslinux-common or pxelinux packages they are the same version - 6.03. I tried netbooting and grabbed a screencap from both 2.4.2 and 2.6.0 on the same network alternately with the same machine. Here's the results:
2.4.2: https:/ /imgur. com/dv2ZSLs
2.6.0: https:/ /imgur. com/rrPSMKi