| 2017-01-10 15:48:28 |
George Shuklin |
description |
If node is in the wait call-back state there is no way for administrator to abort this operation. I believe it should be, because administrator should be able to cancel any pending operations on the node.
Steps to reproduce:
Put node to wait call-back state.
Call:
ironic --ironic-api-version 1.22 node-set-maintenance $uuid on
ironic --ironic-api-version 1.22 node-set-provision-state a93c9183-c057-46e4-a314-2e6982523c4d abort
Expected behavior: node in some kind of fail state which can be moved to manage mode later.
Actual behavior:
The requested action "abort" can not be performed on node "a93c9183-c057-46e4-a314-2e6982523c4d" while it is in state "wait call-back". (HTTP 400) |
If node is in the wait call-back state there is no way for administrator to abort this operation. I believe it should be, because administrator should be able to cancel any pending operations on the node.
Steps to reproduce:
Put node to wait call-back state.
Call:
ironic --ironic-api-version 1.22 node-set-maintenance $uuid on
ironic --ironic-api-version 1.22 node-set-provision-state a93c9183-c057-46e4-a314-2e6982523c4d abort
Expected behavior: node in some kind of fail state which can be moved to manage mode later.
Actual behavior:
The requested action "abort" can not be performed on node "a93c9183-c057-46e4-a314-2e6982523c4d" while it is in state "wait call-back". (HTTP 400)
version: newton |
|
