Comment 12 for bug 1318567

Reason: node-1 do not erased and rebooted. No error in logs. No filesystem mounted like RO. For some reason mcollec

Good answer (when we start deploy, but without reboot):

MC agent 'erase_node', method 'erase_node', results: {:sender=>"1", :statuscode=>0, :statusmsg=>"OK", :data=>{:status=>0, :erased=>nil, :rebooted=>false, :debug_msg=>["Create file for discovery preventing /var/run/nodiscover"], :error_msg=>nil}}

MC agent 'erase_node', method 'erase_node', results: {:sender=>"1", :statuscode=>0, :statusmsg=>"OK", :data=>{:status=>0, :debug_msg=>["Create file for discovery preventing /var/run/nodiscover"], :error_msg=>nil, :erased=>nil, :rebooted=>true}}

Bad answer(but look correct):

MC agent 'erase_node', method 'erase_node', results: {:sender=>"1", :statuscode=>0, :statusmsg=>"OK", :data=>{:status=>0, :erased=>nil, :rebooted=>false, :debug_msg=>["Create file for discovery preventing /var/run/nodiscover"], :error_msg=>nil}}

We erase node 3 times and last or prelast attempt was fail. Maybe for some reason reboot mechanic do not work, but this code also used when we remove or reset env.

And cobbler says what node was rebooted.

2014-07-29 16:43:07 DEBUG
[394] Successfully rebooted: node-1
2014-07-29 16:43:07 DEBUG
[394] Reboot task status: node: node-1 status: [1406648575.853949, "Power management (reboot)", "complete", []]
2014-07-29 16:43:02 DEBUG
[394] Reboot task status: node: node-1 status: [1406648575.853949, "Power management (reboot)", "running", []]
2014-07-29 16:42:57 DEBUG
[394] Reboot task status: node: node-1 status: [1406648575.853949, "Power management (reboot)", "running", []]

Also file /var/run/nodiscover was created

[root@bootstrap ~]# ls -all /var/run/nodiscover
-rw-r--r-- 1 root root 0 2014-07-29 15:42 /var/run/nodiscover

We have some strange moment with time (1 hour different), but no errors. If try to reboot nodes by hands, it will provisioned without problem. I suppose Cobbler could not successfully reboot node for some reason.