I'm not a dev but this seems strange: > 2014-12-03 12:20:46,612 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (Job-Executor-166:ctx-d915e890 ctx-d7a11540) Removing pool Pool[208|IscsiLUN] from avoid set, must have been inserted when searching for another disk's tag > 2014-12-03 12:20:46,614 DEBUG [o.a.c.s.a.AbstractStoragePoolAllocator] (Job-Executor-166:ctx-d915e890 ctx-d7a11540) Checking if storage pool is suitable, name: null ,poolId: 208 > 2014-12-03 12:20:46,617 DEBUG [c.c.s.StorageManagerImpl] (Job-Executor-166:ctx-d915e890 ctx-d7a11540) Checking pool 208 for storage, totalSize: 1520242262016, usedBytes: 865985363968, usedPct: 0.569636422828828, disable threshold: 0.95
First it puts pool 208 into avoid set, then it tries to check it. Hopefully someone who knows the code a bit could clarify if this is intended or a bug. -- Erik On Fri, Dec 5, 2014 at 2:02 PM, France <mailingli...@isg.si> wrote: > Hi guys, > > can someone please look at the exemption from the log and confirm this is > a bug and not misconfiguration. If we are on the road to 4.3.2 release, it > might get fixed and included in it. > Thank you! > > The bug report is here: > https://issues.apache.org/jira/browse/CLOUDSTACK-8014 > > Regards, > F. > >
