As per the state machine, ironic doesn't provide an option to move from CLEANFAIL to CLEAN

Bug #1441445 reported by Anusha on 2015-04-08
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

According to the state machine, there is an option to move from CLEANFAIL to CLEAN using 'clean' verb.

But currently, there is no support in ironic and python-ironicclient , to be accept 'clean' as a valid verb in
node-set-provision-state .

NOTE: There is still workaround , when the node is in CLEANFAIL -> MANAGEABLE -> CLEANING-> AVAILABLE using 'manage' and 'provide' verbs.

Dmitry Tantsur (divius) wrote :

Right, the verb should be "provide", not "clean"

Changed in ironic:
status: New → Triaged
importance: Undecided → High
tags: added: kilo-rc-potential
devananda (devananda) on 2015-04-21
Changed in ironic:
importance: High → Medium
tags: removed: kilo-rc-potential
devananda (devananda) wrote :

As per the state machine specification, there should not be a transition from CLEANFAIL -> CLEANING directly, and so the REST API is correct. That the internal state machine represents this transition is a bug and should be fixed in Liberty, but there's no need to back port it as this is not exposed in the Kilo API. I have removed that tag, and will close this bug. I have opened a new one here:

For reference, I'll quote the spec here as well.

    Nodes in the CLEANING state are being scrubbed in preparation to being made AVAILABLE. Good candidates for CLEANING tasks include:
    Management of CLEANING tasks should be handled in the same fashion as ZAPPING tasks.

    Nodes that transition into ZAPFAIL will automatically enter maintenance mode, as failure to ZAP a machine usually indicates a hardware failure or something else that requires remote hands to fix.

Changed in ironic:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers