[CLOUDSTACK-3367] When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 4.1.0, 4.2.0, 4.5.0, 4.3.1
• Fix Version/s: Future
• Component/s: Management Server, XenServer
• Security Level: Public (Anyone can view this level - this is the default.)
• Environment: CentOS 6.3, XenServer 6.0.2 + all hotfixes, CloudStack 4.1.0
• Assignee: Unassigned
• Reporter: France
• Created: 04/Jul/13 15:31
• Updated: 10/Feb/16 04:52

Description

As the title says: if only one of the primary storages fails, all XenServer hosts get rebooted one by one. Because i have many primary storages, which are/were running fine with other VMs, rebooting XenServer Hipervisor is an overkill. Please disable this or implement just stopping/killing the VMs running on that storage and try to re-attach that storage only.

Problem was reported on the mailing list, as well as a workaround for XenServer. So i'm not the only one hit by this "bug/feature". Workaround for now is as follows:

1. Modify /opt/xensource/bin/xenheartbeat.sh on all your Hosts, commenting out the two entries which have "reboot -f"
2. Identify the PID of the script - pidof -x xenheartbeat.sh
3. Restart the Script - kill <pid>
4. Force reconnect Host from the UI, the script will then re-launch on reconnect