PXE boot not working in virtual environment
Bug #1051626 reported by
Scott Moser
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Expired
|
High
|
Unassigned |
Bug Description
Jeroen has a partial solution at
https:/
However, it seems to not be completely sufficient.
The problem I'm seeing are:
a) after installation of maas and 'maas-import-
b.) attempt to pxeboot for enlistment will fail.
Related bugs:
* bug 1047061: dhcpd.conf next-server set to 127.0.0.1
Changed in maas: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
summary: |
- tftp import broken + next-server written wrong |
Changed in maas: | |
importance: | Critical → High |
status: | Confirmed → Triaged |
summary: |
- next-server written wrong + PXE boot not working in virtual environment |
description: | updated |
To post a comment you must log in.
The warning may be due to a related but separate problem: we get multiple wsgi processes. The system that tracks and displays persistent errors does not share its state between those processes.
So to diagnose the pxeboot problem we'll still need to know what other error you're hitting.