Lost control of nodes with amt driver after user reboot
Bug #1436824 reported by
Tan Lin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Medium
|
Tan Lin |
Bug Description
Problem:
There are two cases of reboot:
1. Reboot by Ironic.
2. Reboot by users who logging into the instance.
There is no problem for case one. The issue is in case two. And this is something related to AMT firmware. So the solution is deploy amt_driver with localboot.
Why:
This is because AMT firmware doesn't support setting pxe as boot device persistent. Once reboot by the user, the node will boot from disk.
Solution:
Enable pxe_amt driver with localboot and enroll nodes with boot_option=local
Changed in ironic: | |
assignee: | nobody → Tan Lin (tan-lin-good) |
description: | updated |
Changed in ironic: | |
milestone: | none → kilo-rc1 |
importance: | Undecided → Medium |
description: | updated |
Changed in ironic: | |
status: | In Progress → Fix Committed |
Changed in ironic: | |
status: | Fix Committed → Fix Released |
Changed in ironic: | |
milestone: | kilo-rc1 → 2015.1.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/167975
Review: https:/