cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9509) KVM Hosts connect with no storage
Date Tue, 27 Sep 2016 07:51:20 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15525400#comment-15525400
] 

ASF GitHub Bot commented on CLOUDSTACK-9509:
--------------------------------------------

GitHub user rhtyd opened a pull request:

    https://github.com/apache/cloudstack/pull/1694

    CLOUDSTACK-9509: Host Connects Without Storage

    KVM hosts on shared storage failure was accepted by mgmt server with the
    host state as Up, even though there was no primary/shared storage available on
    it. This patch offers a quick fix by throwing an exception in the storage monitor
    which connects storage pool on host. The failure is trapped by agent manager
    that disconnects the agent without any investigation.
    
    Based on Lab tests, KVM agent may take upto 2 minutes to attempt NFS mount when
    the storage is inaccessible (firewalled, or shutdown) before returning back with
    an error. It is safe to assume that this won't add pressure on mgmt server due to
    several reconnection attempts, and KVM agent would retry reconnection every 2
    minutes.
    
    For such KVM hosts, where failure happens due to storage issues; they will be
    briefly put in Alert state but will be mostly be in Connecting state during which
    the KVM host attempts to mount/reconfigure NFS storage pool.
    
    /cc @jburwell @karuturi 
    @blueorangutan package

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/shapeblue/cloudstack kvm-no-storage-failfast

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1694.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1694
    
----
commit e13e40ee9cc664ec9d326c8b6fae0c76f6adc01a
Author: Rohit Yadav <rohit.yadav@shapeblue.com>
Date:   2016-06-07T06:11:16Z

    CLOUDSTACK-9509: Host Connects Without Storage
    
    KVM hosts on shared storage failure was accepted by mgmt server with the
    host state as Up, even though there was no primary/shared storage available on
    it. This patch offers a quick fix by throwing an exception in the storage monitor
    which connects storage pool on host. The failure is trapped by agent manager
    that disconnects the agent without any investigation.
    
    Based on Lab tests, KVM agent may take upto 2 minutes to attempt NFS mount when
    the storage is inaccessible (firewalled, or shutdown) before returning back with
    an error. It is safe to assume that this won't add pressure on mgmt server due to
    several reconnection attempts, and KVM agent would retry reconnection every 2
    minutes.
    
    For such KVM hosts, where failure happens due to storage issues; they will be
    briefly put in Alert state but will be mostly be in Connecting state during which
    the KVM host attempts to mount/reconfigure NFS storage pool.
    
    Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>

----


> KVM Hosts connect with no storage
> ---------------------------------
>
>                 Key: CLOUDSTACK-9509
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9509
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>            Priority: Critical
>             Fix For: 4.8.1, 4.10.0.0, 4.9.1.0
>
>
> KVM hosts on shared storage failure was accepted by mgmt server with the
> host state as Up, even though there was no primary/shared storage available on it. They
fail the ModifyStoragePoolCommand, but the management server continues on with adding SSH
keys and marking them as up.



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

Mime
View raw message