You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sangeetha Hariharan (JIRA)" <ji...@apache.org> on 2014/11/14 14:52:33 UTC

[jira] [Reopened] (CLOUDSTACK-5578) KVM - Network down - When the host looses network connectivity , it is not able to fence itself.

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-5578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sangeetha Hariharan reopened CLOUDSTACK-5578:
---------------------------------------------

Hi Kishan,

This is a problem that KVM host is not able to reboot itself which is the expected behavior.

The host is attempting to reboot which fails . Is it possible to make the host forcefully reboot in such cases?

Thanks
Sangeetha

> KVM - Network down - When the host looses network connectivity , it is not able to fence itself.
> ------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5578
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5578
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: Build from 4.3
>            Reporter: Sangeetha Hariharan
>            Assignee: Kishan Kavala
>            Priority: Critical
>             Fix For: 4.5.0
>
>         Attachments: DisconnectedHost.png, kvm-hostdisconnect.rar
>
>
> KVM - Network down - When the host looses network connectivity , it is not able to fence itself.
> Steps to reproduce the problem:
> Set up - Advanced zone with 2 Rhel 6.3 hosts in cluster.
> Deploy ~10 Vms.
> Simulate network disconnect on the host ( ifdown em1)
> Host gets marked as "Down" and all the Vms gets HA-ed to the other host.
> On the KVM host which lost connectivity , attempt to shutdown itself fails.
> It was not able to umount the primary store.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)