[jira] [Updated] (CLOUDSTACK-3367) When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-3367: --- Assignee: Abhinandan Prateek > 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, 4.5.0, 4.3.1 > Environment: CentOS 6.3, XenServer 6.0.2 + all hotfixes, CloudStack > 4.1.0 >Reporter: France >Assignee: Abhinandan Prateek > 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 > 4. Force reconnect Host from the UI, the script will then re-launch on > reconnect -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-3367) When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-3367: --- Issue Type: Improvement (was: Bug) > 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: Improvement > 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 > > 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 > 4. Force reconnect Host from the UI, the script will then re-launch on > reconnect -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3367) When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-3367: --- Fix Version/s: Future > 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: Improvement > 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 > 4. Force reconnect Host from the UI, the script will then re-launch on > reconnect -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3367) When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] France updated CLOUDSTACK-3367: --- Issue Type: Bug (was: Improvement) > 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 > 4. Force reconnect Host from the UI, the script will then re-launch on > reconnect -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3367) When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Animesh Chaturvedi updated CLOUDSTACK-3367: --- Priority: Critical (was: Major) > 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 >Priority: Critical > 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 > 4. Force reconnect Host from the UI, the script will then re-launch on > reconnect -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3367) When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex Huang updated CLOUDSTACK-3367: --- Priority: Major (was: Critical) > 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 > 4. Force reconnect Host from the UI, the script will then re-launch on > reconnect -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CLOUDSTACK-3367) When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koushik Das updated CLOUDSTACK-3367: Assignee: (was: Koushik Das) > 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 > 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)
[jira] [Updated] (CLOUDSTACK-3367) When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] France updated CLOUDSTACK-3367: --- Affects Version/s: 4.3.1 4.5.0 > 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, 4.5.0, 4.3.1 > 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 > 4. Force reconnect Host from the UI, the script will then re-launch on > reconnect -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (CLOUDSTACK-3367) When one primary storage fails, all XenServer hosts get rebooted, killing all VMs, even those not on this primary storage.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinandan Prateek updated CLOUDSTACK-3367: --- Assignee: (was: Abhinandan Prateek) > 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, 4.5.0, 4.3.1 > 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 > 4. Force reconnect Host from the UI, the script will then re-launch on > reconnect -- This message was sent by Atlassian JIRA (v6.3.4#6332)
