pxe_ilo and iscsi_ilo driver sets capabilities:boot_mode in node property if there is none
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
High
|
Shivanand Tendulker |
Bug Description
In Juno release, pxe_ilo and iscsi_ilo drivers sets capabilities:
Problem: capabilities:
When this property is not populated by the user, drivers make the choice of boot mode and is populating that value into the node property.
Due to this behavior, if a user wants to redeploy a node with different boot mode, he/she has to do ironic node-update to either remove the node capabilities added by the ilo driver or replace the node capabilities with the new boot mode.
Steps to reproduce:-
1. Proliant node having ability to boot into BIOS and UEFI is configured for pxe_ilo driver. No capabilities:
2. In the absence of capabilities:
3. While deployoing driver updates the node properties to 'capabilities:
4. Tear down the deployed node
5. The node property 'capabilities:
6. Henceforth, this node would not get selected if the flavor has extra_specs requesting 'capabilities:
Workaround:-
If user have to wants to deploy the node using boot mode that is not being set into node capabilities:
tags: | added: ilo-drivers |
summary: |
- pxe_ilo driver sets capabilities:boot_mode if there is none + pxe_ilo driver sets capabilities:boot_mode in node property if there is + none |
summary: |
- pxe_ilo driver sets capabilities:boot_mode in node property if there is - none + pxe_ilo and iscsi_ilo driver sets capabilities:boot_mode in node + property if there is none |
description: | updated |
description: | updated |
tags: |
added: ilo juno-backport-potential removed: ilo-drivers |
Changed in ironic: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in ironic: | |
milestone: | none → kilo-rc1 |
status: | Fix Committed → Fix Released |
Changed in ironic: | |
milestone: | kilo-rc1 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/155731
Review: https:/