[ https://issues.apache.org/jira/browse/CLOUDSTACK-9366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Will Stevens resolved CLOUDSTACK-9366. -------------------------------------- Resolution: Fixed Fix Version/s: 4.9.0 > 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 > Fix For: 4.9.0 > > > 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)