cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sudhansu Sahu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-9701) When host is disabled/removed, capacity_state for local storage in op_host_capacity is still enabled
Date Fri, 23 Dec 2016 08:05:58 GMT

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

Sudhansu Sahu updated CLOUDSTACK-9701:
--------------------------------------
    Description: 
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, type, removed from host where type = 'Routing';
+----+----------------+--------------------------------------+---------+---------+---------------------+
| id | name           | uuid                                 | status  | type    | removed
            |
+----+----------------+--------------------------------------+---------+---------+---------------------+
|  1 | 10.102.192.151 | 08a7d52d-a8f1-444d-af99-96413d5e6007 | Up      | Routing | NULL  
             |
|  4 | 10.102.192.153 | 01bc0177-c315-45a3-b545-fb54ad8c577f | Removed | Routing | 2016-10-21
08:03:52 |
|  7 | 10.102.192.153 | 041aa083-e427-4118-916f-fd4f6c3850fb | Removed | Routing | 2016-10-21
12:17:47 |
+----+----------------+--------------------------------------+---------+---------+---------------------+
3 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
|
+---------+---------------+-------------------+----------------+---------------+----------------+
|       5 |             0 |                 0 |  1982127407104 |             9 | Enabled 
      |
|       6 |             0 |                 0 |  1982127407104 |             9 | Enabled 
      |
+---------+---------------+-------------------+----------------+---------------+----------------+
2 rows in set (0.00 sec)
{noformat}

  was:


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, type, removed from host where type = 'Routing';
---------------------------------------------------------------------------------------+
id 	name 	uuid 	status 	type 	removed

---------------------------------------------------------------------------------------+
1 	10.102.192.151 	08a7d52d-a8f1-444d-af99-96413d5e6007 	Up 	Routing 	NULL
4 	10.102.192.153 	01bc0177-c315-45a3-b545-fb54ad8c577f 	Removed 	Routing 	2016-12-21 08:03:52
7 	10.102.192.153 	041aa083-e427-4118-916f-fd4f6c3850fb 	Removed 	Routing 	2016-12-21 12:17:47

---------------------------------------------------------------------------------------+
3 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

--------------------------------------------------------------------------------+
5 	0 	0 	1982127407104 	9 	Enabled
6 	0 	0 	1982127407104 	9 	Enabled

--------------------------------------------------------------------------------+
2 rows in set (0.00 sec)
{noformat}


> 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, type, removed from host where type = 'Routing';
> +----+----------------+--------------------------------------+---------+---------+---------------------+
> | id | name           | uuid                                 | status  | type    | removed
            |
> +----+----------------+--------------------------------------+---------+---------+---------------------+
> |  1 | 10.102.192.151 | 08a7d52d-a8f1-444d-af99-96413d5e6007 | Up      | Routing | NULL
               |
> |  4 | 10.102.192.153 | 01bc0177-c315-45a3-b545-fb54ad8c577f | Removed | Routing | 2016-10-21
08:03:52 |
> |  7 | 10.102.192.153 | 041aa083-e427-4118-916f-fd4f6c3850fb | Removed | Routing | 2016-10-21
12:17:47 |
> +----+----------------+--------------------------------------+---------+---------+---------------------+
> 3 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
|
> +---------+---------------+-------------------+----------------+---------------+----------------+
> |       5 |             0 |                 0 |  1982127407104 |             9 | Enabled
       |
> |       6 |             0 |                 0 |  1982127407104 |             9 | Enabled
       |
> +---------+---------------+-------------------+----------------+---------------+----------------+
> 2 rows in set (0.00 sec)
> {noformat}



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

Mime
View raw message