Comment 6 for bug 1543221

Tipycally illegal opcode means that bootloader wasn't installed properly for some reasons. But we're wiping out with zeroes the beginning and the end of any disk presented in the system. So, BIOS/UEFI/whatever code jumps to boot sector and then CPU suddenly will realize that opcode isn't correct by any means.

node-2 and node-3 weren't provisioned. fuel-agent complained about improper disk partitioning scheme and exited.

http://paste.openstack.org/show/486318/

looks like a bug in fuel-agent. Requires diving into logs and the code.

Also, interesting messages in astute.log

2016-02-08 17:10:13 DEBUG [723] Task time summary: reboot_provisioned_nodes with status error on node 1 took 00:04:00
2016-02-08 17:10:13 DEBUG [723] Task time summary: reboot_provisioned_nodes with status error on node 4 took 00:04:00
2016-02-08 17:10:13 DEBUG [723] Task time summary: reboot_provisioned_nodes with status error on node 5 took 00:04:00
2016-02-08 17:10:13 DEBUG [723] Task time summary: reboot_provisioned_nodes with status error on node 6 took 00:04:00

Nodes 1,4,5,6 were provisioned without errors.

@Sergey Galkin (sgalkin),
Are you sure that all nodes were unable to boot and showed red screen of death?