Details
-
Bug
-
Status: Reviewable
-
Major
-
Resolution: Unresolved
-
4.5.2, 4.6.0
-
None
-
None
-
Security Level: Public (Anyone can view this level - this is the default.)
-
None
Description
This issue occurs when a volume in Ready state is moved across storage pools.
Let us say there is a data volume, volume0 in Ready state in a cluster scope primary storage primary0.
Now, when an operation is attempted to attach this volume to a vm in another cluster, the volume is moved to the new cluster and the asking size is zero at this time.
you can observe logs like below with asking size 0 in the management server logs.
2015-09-22 08:49:02,754 DEBUG [c.c.s.StorageManagerImpl] (Work-Job-Executor-6:ctx-27e0990a job-37/job-38 ctx-985e5ad0) (logid:a0a97129) Checking pool: 1 for volume allocation [Vol[8|vm=null|DATADISK]], maxSize : 3298534883328, totalAllocatedSize : 24096276480, askingSize : 0, allocated disable threshold: 0.85
Attachments
Issue Links
- links to
