Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 31 Mar 2017 16:48:41 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13030321.1482480260000.177673.1490978921713@Atlassian.JIRA>
In-Reply-To: <JIRA.13030321.1482480260000@Atlassian.JIRA>
References: <JIRA.13030321.1482480260000@Atlassian.JIRA> <JIRA.13030321.1482480260266@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-9701) When host is disabled/removed,
 capacity_state for local storage in op_host_capacity is still enabled
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 31 Mar 2017 16:48:47 -0000


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

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

Github user mrunalinikankariya commented on the issue:

    https://github.com/apache/cloudstack/pull/1869
  
    Test LGTM, tested using marvin test script


> When host is disabled/removed, capacity_state for local storage in op_host_capacity is still enabled
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9701
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9701
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.9.0
>            Reporter: Sudhansu Sahu
>            Assignee: Sudhansu Sahu
>
> Setup: Advanced zone with local storage enabled
> Description
> =========
> When a host is disabled or removed, local storage related capacity data for the corresponding local storage of the host is still in enabled state.
> This may not directly impact deploy VM functionality (for example) but it does show incorrect capacity calculations.
> Steps
> =====
> 1. Enable local storage for zone
> 2. Disable host or remove host (after adding it to maintenance mode)
> 3. Check op_host_capacity (capacity_state=9)
> In either of the cases, the local storage related capacity is still enabled for the host.
> {noformat}
> mysql> select id, name, uuid, status,resource_state, type, removed from host where type = 'Routing';
> +----+--------------------+--------------------------------------+--------+----------------+---------+---------+
> | id | name               | uuid                                 | status | resource_state | type    | removed |
> +----+--------------------+--------------------------------------+--------+----------------+---------+---------+
> |  1 | xenserver-nvjxksqs | 16a922d0-7b4c-4c84-baad-5bd91542181c | Up     | Disabled       | Routing | NULL    |
> |  4 | xenserver-hnkwhblp | 0e0f161a-7cf5-4e44-8bcc-a25ba7d798e5 | Up     | Enabled        | Routing | NULL    |
> +----+--------------------+--------------------------------------+--------+----------------+---------+---------+
> 2 rows in set (0.00 sec)
> mysql> select host_id, used_capacity, reserved_capacity, total_capacity, capacity_type, capacity_state from op_host_capacity where capacity_type=9;
> +---------+---------------+-------------------+----------------+---------------+----------------+
> | host_id | used_capacity | reserved_capacity | total_capacity | capacity_type | capacity_state |
> +---------+---------------+-------------------+----------------+---------------+----------------+
> |       3 |       4194304 |                 0 |   491505319936 |             9 | Enabled        |
> |       4 |       4194304 |                 0 |   491505319936 |             9 | Enabled        |
> +---------+---------------+-------------------+----------------+---------------+----------------+
> 2 rows in set (0.00 sec)
> mysql> select id, name, removed, pool_type, capacity_bytes from storage_pool where id in (3,4);
> +----+----------------------------------+---------+-----------+----------------+
> | id | name                             | removed | pool_type | capacity_bytes |
> +----+----------------------------------+---------+-----------+----------------+
> |  3 | xenserver-nvjxksqs Local Storage | NULL    | LVM       |   491505319936 |
> |  4 | xenserver-hnkwhblp Local Storage | NULL    | LVM       |   491505319936 |
> +----+----------------------------------+---------+-----------+----------------+
> {noformat}


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)