| 2015-02-05 05:03:28 |
Shivanand Tendulker |
bug |
|
|
added bug |
| 2015-02-05 05:03:55 |
Shivanand Tendulker |
tags |
|
ilo-drivers |
|
| 2015-02-05 05:06:01 |
Shivanand Tendulker |
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 |
|
| 2015-02-05 07:50:05 |
Shivanand Tendulker |
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 |
|
| 2015-02-05 07:51:54 |
Shivanand Tendulker |
description |
In Juno release, pxe_ilo driver sets capabilities:boot_mode to the pending boot mode if this capability is not set on the Node.
Driver should not update this node property. User should populate this property and driver should use it during deploy.
Steps to reproduce:-
1. Proliant node having ability to boot into BIOS and UEFI is configuired for pxe_ilo driver.
2. Say, the current bot mode on the node is configured to 'BIOS'
3. Node is deployed using a flavor that does not have capabilities:boot_mode specified in its extra_specs
4. Node would get deployed using BIOS boot mode and driver updates the node properties to 'capabilities:boot_mode:bios'
5. Tear down the deploy
6. The node property 'capabilities:boot_mode:bios'is retained with the node.
7. Henceforth, this node would not get selected if the flavor has extra_specs requesting 'capabilities:boot_mode:uefi'
Workaround:-
If user have to wants to deploy the node using boot mode that is not being set into node capabilities:boot_mode. change the node properties for capabilities:boot_mode with appropriate boot mode value. |
In Juno release, pxe_ilo and iscsi_ilo drivers sets capabilities:boot_mode to the pending boot mode if this capability is not set on the Node.
Problem: Driver should not update this node property. User should populate this property and driver should use it during deploy.
Due to this issue, 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 configuired for pxe_ilo driver.
2. Say, the current bot mode on the node is configured to 'BIOS'
3. Node is deployed using a flavor that does not have capabilities:boot_mode specified in its extra_specs
4. Node would get deployed using BIOS boot mode and driver updates the node properties to 'capabilities:boot_mode:bios'
5. Tear down the deploy
6. The node property 'capabilities:boot_mode:bios'is retained with the node.
7. Henceforth, this node would not get selected if the flavor has extra_specs requesting 'capabilities:boot_mode:uefi'
Workaround:-
If user have to wants to deploy the node using boot mode that is not being set into node capabilities:boot_mode. change the node properties for capabilities:boot_mode with appropriate boot mode value. |
|
| 2015-02-05 09:20:17 |
Shivanand Tendulker |
description |
In Juno release, pxe_ilo and iscsi_ilo drivers sets capabilities:boot_mode to the pending boot mode if this capability is not set on the Node.
Problem: Driver should not update this node property. User should populate this property and driver should use it during deploy.
Due to this issue, 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 configuired for pxe_ilo driver.
2. Say, the current bot mode on the node is configured to 'BIOS'
3. Node is deployed using a flavor that does not have capabilities:boot_mode specified in its extra_specs
4. Node would get deployed using BIOS boot mode and driver updates the node properties to 'capabilities:boot_mode:bios'
5. Tear down the deploy
6. The node property 'capabilities:boot_mode:bios'is retained with the node.
7. Henceforth, this node would not get selected if the flavor has extra_specs requesting 'capabilities:boot_mode:uefi'
Workaround:-
If user have to wants to deploy the node using boot mode that is not being set into node capabilities:boot_mode. change the node properties for capabilities:boot_mode with appropriate boot mode value. |
In Juno release, pxe_ilo and iscsi_ilo drivers sets capabilities:boot_mode to the boot mode chosen by driver for deploy if this capability is not set in the Node property.
Problem: capabilities:boot_mode is a Node property for user to poluate to facilitate node selection based on flavor extra_spec properties. Drivers use this capability during deploy.
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:boot_mode is populated into node properties.
2. In the absence of capabilities:boot_mode property, node would get deployed in any boot mode. Say it gets deployed in 'bios'
3. While deployoing driver updates the node properties to 'capabilities:boot_mode:bios'
4. Tear down the deployed node
5. The node property 'capabilities:boot_mode:bios'is retained in the node properties.
6. Henceforth, this node would not get selected if the flavor has extra_specs requesting 'capabilities:boot_mode:uefi'
Workaround:-
If user have to wants to deploy the node using boot mode that is not being set into node capabilities:boot_mode. change the node properties for capabilities:boot_mode with appropriate boot mode value. |
|
| 2015-02-09 12:18:17 |
Dmitry Tantsur |
tags |
ilo-drivers |
ilo juno-backport-potential |
|
| 2015-02-09 12:18:32 |
Dmitry Tantsur |
ironic: status |
New |
Triaged |
|
| 2015-02-09 12:18:38 |
Dmitry Tantsur |
ironic: importance |
Undecided |
High |
|
| 2015-02-13 12:35:21 |
OpenStack Infra |
ironic: status |
Triaged |
In Progress |
|
| 2015-02-13 12:35:21 |
OpenStack Infra |
ironic: assignee |
|
Shivanand Tendulker (shivanand-tendulker) |
|
| 2015-03-23 17:50:05 |
OpenStack Infra |
ironic: status |
In Progress |
Fix Committed |
|
| 2015-04-14 07:25:55 |
Thierry Carrez |
ironic: status |
Fix Committed |
Fix Released |
|
| 2015-04-14 07:25:55 |
Thierry Carrez |
ironic: milestone |
|
kilo-rc1 |
|
| 2015-04-30 10:07:22 |
Thierry Carrez |
ironic: milestone |
kilo-rc1 |
2015.1.0 |
|
