<fix>[localstorage]: ZSTAC-84163 check capacity by target primary storage - #4689
<fix>[localstorage]: ZSTAC-84163 check capacity by target primary storage#4689MatheMatrix wants to merge 1 commit into
Conversation
|
Important Review skippedThis review includes 5 billable files. This on-demand review is free during your promotion. Your included review limit has been reached. Run
⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
You can disable this status message by setting the Warning
|
48d6932 to
ddad333
Compare
…rage Root Cause: LocalStorageAllocatorFactory used HostAllocatorSpec.getDiskSize() to check every local storage host ref. The value was the total size of root and data disks, so disks assigned to non-local primary storage were also counted against local storage and could incorrectly filter out a valid host. Solution: Carry root and data disk capacity requirements as primary-storage UUID and size tuples. Local storage sums requirements assigned to the current local primary storage. When the host cluster only attaches local storage, add only the capacity of disks whose primary storage is undetermined, instead of counting disks already assigned to another primary storage. Migration uses the same per-primary-storage calculation because its producer records the destination primary storage with the migration capacity. Test: Update CreateVmHostAllocateCase to cover insufficient all-local capacity, mixed local/NFS placement, and partially undetermined primary storage. Verified with: Not run as requested. Resolves: ZSTAC-84163 Change-Id: I3f9895c605819a570a580cedfeaf1d80db300c80
ddad333 to
f01e018
Compare
Root Cause:
LocalStorageAllocatorFactory used HostAllocatorSpec.getDiskSize() to check every local storage host ref. The value was the total size of root and data disks, so disks assigned to non-local primary storage were also counted against local storage and could incorrectly filter out a valid host.
Solution:
Carry root and data disk capacity requirements as primary-storage UUID and size tuples. Local storage sums requirements assigned to the current local primary storage. If any requirement has no determined primary storage and the host cluster only attaches local storage, retain the conservative total-size check. Migration uses the same per-primary-storage calculation because its producer records the destination primary storage with the migration capacity.
Test:
Update CreateVmHostAllocateCase to cover insufficient all-local capacity, mixed local/NFS placement, and partially undetermined primary storage.
Verified with:
Not run as requested.
Resolves: ZSTAC-84163
Change-Id: I3f9895c605819a570a580cedfeaf1d80db300c80
sync from gitlab !10742