reboot required/commit required are conflated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-dracclient |
Fix Released
|
High
|
Christopher Dearborn |
Bug Description
In WSMAN, certain setter/creater methods return two values. One indicates if the server needs to be rebooted to have the changes applied (RebootRequired), and the other indicates if a configuration job needs to be created to have the changes applied (SetResults).
Currently in python-dracclient, only commit_required is returned and the value of it indicates if a reboot is required. The value of this parameter should indicate if a configuration job needs to be created, not if a reboot is required, and an additional parameter should be returned that indicates if reboot is required.
The reason that this works at the present time is because apparently both a reboot and a configuration job are required when setting BIOS settings. This is not the case though with iDRACCardSettings.
In addition, the possible values of reboot required are currently only True and False. While this is true for BIOS settings, it is not true when performing RAID operations. RAID operations can return "YES", "NO", and "OPTIONAL" from the iDRAC.
We need to modify python-dracclient to return indicators of when a configuration job needs to be created as well as when a server needs to be rebooted. These indicators should be separate and distinct. The value of the reboot required indicator should allow 3 possible return values, not just 2.
Changed in python-dracclient: | |
assignee: | nobody → Christopher Dearborn (cdearbor) |
importance: | Undecided → High |
status: | New → In Progress |
Fix proposed to branch: master /review. openstack. org/520225
Review: https:/