Bug 1397951

Summary: VMware Auto Placement issue with insufficient space on Datastore
Product: Red Hat CloudForms Management Engine Reporter: Leo Khomenko <lkhomenk>
Component: ProvidersAssignee: Adam Grare <agrare>
Status: CLOSED CURRENTRELEASE QA Contact: Leo Khomenko <lkhomenk>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: anewman, cpelland, gblomqui, jfrey, jhardy, lkhomenk, obarenbo, simaishi
Target Milestone: GAKeywords: FutureFeature, TestOnly, ZStream
Target Release: 5.8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage:vmware
Fixed In Version: 5.8.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1404454 1404455 (view as bug list) Environment:
Last Closed: 2017-06-12 17:13:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: VMware Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1404454, 1404455    

Description Leo Khomenko 2016-11-23 16:14:59 UTC
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:
Datacenters:
    test_datacenter:
        Clusters:
            test_cluster:
                only_1_host_with_datastorage_smaller_200Mb
    CFME:
        Clusters:
            CFME_Cluster:
                4_hosts_with_plenty_available_datastorages
            

Version-Release number of selected component (if applicable):5.6.3.1


How reproducible:7/7


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?

Comment 11 Adam Grare 2016-11-30 20:09:58 UTC
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.

Comment 13 CFME Bot 2016-12-01 14:36:25 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/a6c20ccbffec30695221174023417eccab2bf670

commit a6c20ccbffec30695221174023417eccab2bf670
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.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1397951

 .../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(-)

Comment 16 Leo Khomenko 2017-02-06 17:18:04 UTC
verified on 5.6.4.0