Description of problem:it's possible to get error during VM provisioning as Auto Placement select's Datastorage with a lack of free space.
Environment available options:
Version-Release number of selected component (if applicable):18.104.22.168
Steps to Reproduce:
1.Provision a VM to VC with a setup like described above using Auto Placement
Actual results:error - insufficient space
Expected results:VM successfully provisioned
Additional info: PLease share info on Auto Placement. Do we have docs on it?
Is it supposed to check option from below? e.g. - check available space on datastores and only based on this check hosts/clusters that provide this datastore?
Since we do consider free_space as part of the auto-placement method I'm changing this from an RFE to a Bug. We should not be considering hosts that do not have a datastore large enough to hold the VM to be provisioned.
New commit detected on ManageIQ/manageiq/master:
Author: Adam Grare <agrare>
AuthorDate: Wed Nov 30 15:06:56 2016 -0500
Commit: Adam Grare <agrare>
CommitDate: Thu Dec 1 08:47:51 2016 -0500
Only consider hosts with large enough datastores
When picking a host and storage for provisioning using the
best_fit_least_utilized method we should only consider hosts that have
storages large enough to hold the new VM.
.../Placement.class/__methods__/microsoft_best_fit_least_utilized.rb | 3 ++-
.../Placement.class/__methods__/vmware_best_fit_least_utilized.rb | 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
verified on 22.214.171.124