cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koushik Das" <>
Subject Review Request: CLOUDSTACK-803: HA gets triggered even when the host investigator is unable to determine the state of the host
Date Mon, 07 Jan 2013 05:47:40 GMT

This is an automatically generated e-mail. To reply, visit:

Review request for cloudstack and Alex Huang.


CS tries to do HA on VMs if it finds that the host on which they are running is down. HA should
only happen when CS is able to determine (host investigators return status as 'Down') that
host is down. Currently due to a bug in code even if the hosts investigators are unable to
determine state (returns 'null'), HA gets triggered.
This results in unnecessary HA of VMs.

The fix is to not do HA in case the state of host cannot be determined.

This addresses bug CLOUDSTACK-803.


  server/src/com/cloud/agent/manager/ 8141fdb 



I did the following manual testing

-	Setup advanced zone with XS host
-	Created a VM
-	Pulled out network cable for MS
-	Checked in the debugger that the DisconnectTask is running
-	This calls  handleDisconnectWithInvestigation in AgentManagerImpl
-	In the debugger saw that the following line of code is returning state as null 'final Status
determinedState = investigate(attache);'
-	So the warning message added is seen 's_logger.warn("Agent state cannot be determined, do
-	The above steps continues in a loop till the time I plug the network cable back after which
again the status of the host gets correctly determined by the investigator.

If either the XS host or MS is disconnected from network then investigator cannot determine
the state of the host and so based on the fix HA won’t be triggered.

Sowmya from Citrix QA team also did additional testing for this on a private branch.


Koushik Das

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message