You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Chip Childers (JIRA)" <ji...@apache.org> on 2013/06/04 20:55:50 UTC
[jira] [Updated] (CLOUDSTACK-155) HA checks lead to unnecessary
Compute Node reboot when Primary Storage is in Maintenance Mode
[ https://issues.apache.org/jira/browse/CLOUDSTACK-155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chip Childers updated CLOUDSTACK-155:
-------------------------------------
Fix Version/s: (was: 4.1.0)
4.2.0
> HA checks lead to unnecessary Compute Node reboot when Primary Storage is in Maintenance Mode
> ---------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-155
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-155
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: KVM, Volumes
> Affects Versions: pre-4.0.0
> Reporter: Jarosław Dzbęk
> Assignee: edison su
> Fix For: 4.2.0
>
> Attachments: ha.log
>
>
> We are using Cloudstack 3.0.2 using KVM on Ubuntu 12.04 with PrimaryStorage over NFS
> When we enable Maintenance Mode on a PrimaryStorage and disconnect the storage machine for reconfiguration the heartbeat checks on the KVM lead to an unwanted reboot of KVM Compute Nodes.
> The /usr/lib64/cloud/agent/scripts/vm/hypervisor/kvm/kvmheartbeat.sh script is correctly identifying a persistent problem with the disconnected storage pool. The problem is that this pool was intentionally put into maintenance mode and MAY be unavailable.
--
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