[
https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917862#comment-13917862
]
Koushik Das commented on CLOUDSTACK-3367:
-----------------------------------------
Busy with some other stuff, unassigned so that it can be picked up by anyone
else willing to work on it. Initially had planned to fix it as part of
CLOUDSTACK-5203 (
https://cwiki.apache.org/confluence/display/CLOUDSTACK/User+VM+HA+using+native+XS+HA+capabilities)
but that proposal was dropped due to regressions
(http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201311.mbox/%3c20cf38cb4385ce4d9d1558d52a0fc05818f...@sjcpex01cl03.citrite.net%3E).
> When one primary storage fails, all XenServer hosts get rebooted, killing all
> VMs, even those not on this primary storage.
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3367
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3367
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, XenServer
> Affects Versions: 4.1.0, 4.2.0
> Environment: CentOS 6.3, XenServer 6.0.2 + all hotfixes, CloudStack
> 4.1.0
> Reporter: France
> Fix For: Future
>
>
> 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
--
This message was sent by Atlassian JIRA
(v6.2#6252)
