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-9366) Disable a host also disables storage pool capacity
Date Mon, 02 May 2016 16:36:12 GMT

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

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

Github user swill commented on the pull request:

    https://github.com/apache/cloudstack/pull/1516#issuecomment-216286395
  
    We are missing one code review on this one.


> Disable a host also disables storage pool capacity
> --------------------------------------------------
>
>                 Key: CLOUDSTACK-9366
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9366
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.8.0
>            Reporter: Sudhansu Sahu
>            Assignee: Sudhansu Sahu
>
> Disable and Remove Host operation disables the primary storage capacity.
> Steps to replicate:
> Base Condition: There exists a host and storage pool with same id
> Steps:
> 1. Find a host and storage pool having same id
> 2. Disable the host
> 3. verify that the CPU(1) and MEMORY(0) capacity in op_host_capacity for above host is
disabled
> 4. verify that the STORAGE(3) capacity in op_host_capacity for storage pool with id same
as above host is also disabled
> RCA:
> 'host_id' column in 'op_host_capacity' table used for storing both storage pool id (for
STORAGE capacity) and host id (MEMORY and CPU). While removing a HOST we also disable the
capacity associated with host.
> Ideally while disabling capacity we should only disable MEMORY and CPU capacity, but
we are not doing so.
> Code Path:
> ResourceManagerImpl.doDeleteHost() -> ResourceManagerImpl.resourceStateTransitTo()
-> CapacityDaoImpl.updateCapacityState(null, null, null, host.getId(), capacityState.toString())
> updateCapacityState is updating disabling all entries which matches the host_id. This
will also disable a entry having storage pool id same as that of host id.



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

Mime
View raw message