Newer hardware may take much longer to transition power states
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
A discussion over the past weekend led me to an awareness that some pending generations new hardware under development entering hardware qualification labs is forcing lab operators to extend the timeout to consider power state changes to be substantially longer, to the point it was mentioned they scripted a simple test to reproduce the issue and generally saw a machine taking 90 seconds to report "power on", after the machine power had been turned on, which forced them to have to change their ironic.conf.
Obviously, this is not ideal, likely requires a node or resource class level override so it can be asserted for specific types of machines to permit the minute or longer state change, while not waiting that same extended period of time for normal machines changing in 2 to 5 seconds.
Ultimately, this is likely an enhancement, but one we should also consider back porting.
| Julia Kreger (juliaashleykreger) wrote | #1 |
As a note, I mentioned this same issue to someone else and they indicated they too had seen it as well, so it seems like this issue is becoming more and more prevalent and something we likely need to consider addressing moving forward.