Comment 5 for bug 1427211

Note, that at the previous failed BVT #63, there is the same issue with sudden interrupt in puppet logs:
"2015-03-01T07:08:45.532647+00:00 notice: (/Stage[corosync_setup]/Osnailyfacter::Cluster_ha::Virtual_ips/Cluster::Virtual_ips[public_old]/Cluster::Virtual_ip[public_old]/Cs_resource[vip__public_old]/ensure) created"

That should be the some devops environment related issue, perhaps

The stopped state of resources after the failed deployment is no issue, it is ensured by astute orchestrator - there are 3 controller nodes in cluster, but no quorum in Corosync, so no-quorum-policy=stopped stops all resources as expected.