server: create DB entry for storage pool capacity when create storage pool#4805
Conversation
| throw new CloudRuntimeException("Failed to add data store: " + e.getMessage(), e); | ||
| } | ||
|
|
||
| // create entry for storage pool capacity |
There was a problem hiding this comment.
May I know if this specific to any storage type ?
Because I already see the same code creating capacity entries for cluster scoped storage pool and local storage pools.
cluster storage :
Local storage :
There was a problem hiding this comment.
@harikrishna-patnala
I tested with zone-wide storage pools.
do you think it is better to add storageMgr.createCapacityEntry(pool.getId()); at line 176 below ?
There was a problem hiding this comment.
Yes @weizhouapache, that's the only missing piece. Other storage scopes are already handled.
… storage pool" This reverts commit e790167.
|
@blueorangutan package |
|
@harikrishna-patnala a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S] |
|
@blueorangutan package |
|
@shwstppr a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. [S] |
|
Packaging result: ✖️ centos7 ✖️ centos8 ✖️ debian. SL-JID 167 |
|
Packaging result: ✔️ centos7 ✔️ centos8 ✔️ debian. SL-JID 171 |
|
@blueorangutan test |
|
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-199)
|
|
@blueorangutan test |
|
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-244)
|
Description
This PR fixes the issue that new storage pool can not be used in the first few minute after adding to cloudstack.
steps to reproduce the issue
(1) change global setting vm.allocation.algorithm to 'firstfitleastconsumed' (this allocator orders host/storage by capacity, maybe other algorithim has same issue).
(2) create a zone and enable it
(3) systemvm cannot be created, until Capacity Checker runs (it runs every 5 minutes).
Types of changes
Feature/Enhancement Scale or Bug Severity
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?