Fix HA bug when VMs are stopped on agent disconnect (apache#26)

When an agent is disconnected due to a network issue, the HA work kicks
in and stops some VMs. This is a quick fix to avoid restarting any VMs
until the bug is found and fixed.

Author: marcaurele

server/src/com/cloud/ha/HighAvailabilityManagerImpl.java

@@ -273,7 +273,7 @@ public void scheduleRestartForVmsOnHost(final HostVO host, boolean investigate)
                 continue;
             }
             if (s_logger.isDebugEnabled()) {
-                s_logger.debug("Notifying HA Mgr of to restart vm " + vm.getId() + "-" + vm.getInstanceName());
+                s_logger.debug("Notifying HA Mgr of to restart vm " + vm.getId() + "-" + vm.getInstanceName() + " with investigate=" + investigate);
             }
             vm = _instanceDao.findByUuid(vm.getUuid());
             Long hostId = vm.getHostId();
@@ -282,7 +282,9 @@ public void scheduleRestartForVmsOnHost(final HostVO host, boolean investigate)
                         + hostId + " VM HA is done");
                 continue;
             }
-            scheduleRestart(vm, investigate);
+            if (vm.isHaEnabled()) {
+                scheduleRestart(vm, investigate);
+            }
         }
     }
 
@@ -497,7 +499,7 @@ protected Long restart(final HaWorkVO work) {
 
                 boolean fenced = false;
                 if (alive == null) {
-                    s_logger.debug("Fencing off VM that we don't know the state of");
+                    s_logger.debug("Fencing off VM " + vm + " that we don't know the state of");
                     for (FenceBuilder fb : fenceBuilders) {
                         Boolean result = fb.fenceOff(vm, host);
                         s_logger.info("Fencer " + fb.getName() + " returned " + result);