bcf6c12269
While investigating a very curious report, I discovered that if somehow the power was *already* turned off to a node, say through an incorrect BMC *or* human action, and Ironic were to pick it up (as it does by default, because it checks before applying the power state, then it would not wipe the token information, preventing the agent from connecting on the next action/attempt/operation. We now remove the token on all calls to conductor utilities node_power_action method when appropriate, even if no other work is required. Change-Id: Ie89e8be9ad2887467f277772445d4bef79fa5ea1
7 lines
182 B
YAML
7 lines
182 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Fixes an issue where an agent token could be inadvertently orphaned
|
|
if a node is already in the target power state when we attempt to turn
|
|
the node off.
|