[2.0b5] AMT machines using wsman do not netboot
Bug #1580350 reported by
Andres Rodriguez
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Newell Jensen | ||
Bug Description
MAAS turns the machines on but apparently is not telling them to netboot/pxe boot. Full node event log:
Queried node's BMC - Power state queried: on Tue, 10 May. 2016 17:42:56
Queried node's BMC - Power state queried: on Tue, 10 May. 2016 17:37:41
Node powered on Tue, 10 May. 2016 17:33:59
Powering node on Tue, 10 May. 2016 17:33:44
User starting node commissioning - (admin)
Related branches
lp:~newell-jensen/maas/fix-1580350
- Gavin Panella (community): Approve
-
Diff: 355 lines (+152/-40)4 files modifiedsrc/provisioningserver/drivers/power/amt.py (+40/-15)
src/provisioningserver/drivers/power/amt.wsman-boot-config.xml (+13/-0)
src/provisioningserver/drivers/power/amt.wsman-pxe.xml (+12/-0)
src/provisioningserver/drivers/power/tests/test_amt.py (+87/-25)
| description: | updated |
| Changed in maas: | |
| importance: | Undecided → Critical |
| status: | New → Confirmed |
| milestone: | none → 2.0.0 |
Revision history for this message
| Mike Pontillo (mpontillo) wrote | #1 |
| Changed in maas: | |
| assignee: | nobody → Newell Jensen (newell-jensen) |
| Changed in maas: | |
| status: | Confirmed → 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.
It may not be possible to set up network booting with all BMCs. If we can't figure out a way to do this, we'll need to document the workaround: setting up each machine's boot order manually in the BIOS to try the network first, then fall back to the local disk.