John Garbutt d65ca49990 xenapi: deal with reboots while talking to agent ... The latest version of the agent has started changing the hostname through the official windows APIs, when resetnetwork is called. This means a reboot might happen after resetnetwork. A reboot happens when polling for the version. Until now we wait for the call timeout, before fetching the new dom id. This change ensures that if we spot a reboot, the plugin exits early rather than keeping polling the wrong dom id. Turns out its best to wait for the dom_id to change, before trying to poll the agent again. Once the dom_id in xenapi has been updated, the xenstore keys are always in place. Trying too early leads to lots of reboot detections because we are retrying with the old dom_id. XenServer continues to return the old dom_id for a little while after the reboot. Closes-Bug: #1370999 Change-Id: Id0bf5b64f2b271d162db5bbce50167ab1f665c87		2014-09-26 14:57:05 +01:00
..
doc	Improve grammar throughout nova.	2012-04-10 11:15:07 -07:00
networking/etc	Fixed many typos.	2014-04-25 21:47:41 -07:00
xenapi	xenapi: deal with reboots while talking to agent	2014-09-26 14:57:05 +01:00