Comment 3 for bug 1373988

If we talk about provisioning operation, first mcollective operation will be 'erase_node' from mcollective 'erase_node' agent.
And we do not analyze problem in this step, for example with inaccessible or error nodes. In first minutes after starting deploy we can got only error about problem with rebooting (but without mcollective erasing we can successfully rebooting and maybe installing OS or got error in this step or just reboot to bootstrap stage again).

To solve this we just need stop deployment if any of nodes got problem with erasing. This one should solve problem.

What do you think?