Bug 1621891

Summary: [RFE] Choose Automatically doesn't behave as expected for RHEV Provider
Product: Red Hat CloudForms Management Engine Reporter: David Luong <dluong>
Component: AutomateAssignee: William Fitzgerald <wfitzger>
Status: CLOSED WONTFIX QA Contact: Angelina Vasileva <anikifor>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.9.3CC: abellott, dluong, dmetzger, gmccullo, mkanoor, mshriver, obarenbo, tfitzger
Target Milestone: GAKeywords: FutureFeature, RFE
Target Release: 5.11.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-18 14:32:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Attachments:
Description Flags
automate method none

Description David Luong 2018-08-23 19:40:37 UTC 
Description of problem:
When provisioning a VM or service for a RHEV provider, there is a restriction the placement when using "Choose Automatically" under environment.  The placement is restricted to the cluster that the template is located on.  However, this is no longer a restriction for RHEV

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

How reproducible:
Always

Steps to Reproduce:
1.  Have a template in one cluster
2.  Repeat provisioning with the Choose 
3.

Actual results:
It always chooses the cluster that the template is located on.

Expected results:
Should be able to provision to any valid cluster/host

Additional info:
Comment 2 Greg McCullough 2018-08-24 13:41:57 UTC 
David - Are you aware of when this changed?  We would need to take different actions based on the RHV version.


The current logic is here:
https://github.com/ManageIQ/manageiq-content/blob/0b7e24fe672647aaa63199d27c9cda65a02f6faa/content/automate/ManageIQ/Infrastructure/VM/Provisioning/Placement.class/__methods__/redhat_best_fit_cluster.rb#L16
Comment 3 Greg McCullough 2018-08-24 13:53:50 UTC 
David - Also want to note that the default auto-placement logic is defined in automate specifically to allow users to modify as needed.  While the current code is not wrong, it could be enhanced so marking as an RFE.

Before this RFE is completed the method can be overridden in a custom domain to meet your needs.
Comment 5 David Luong 2018-08-24 14:39:11 UTC 
Hey Greg,

Sorry, I'm unaware of when this changed, and I cannot seem to find a way to find out when this changed.  However, I did find a (non-working) method in our blog to do this, and it was from 2013, so I'd imagine all supported versions of RHEV allow for this behavior now.

The method I'm talking about is found here:
https://cloudformsblog.redhat.com/2013/09/06/placement-profile-best-fit-cluster-using-tags/

I'll upload the working version to the case if you guys need something to jump off of.
Comment 6 David Luong 2018-08-24 14:41:57 UTC 
Created attachment 1478551 [details]
automate method

This may not be the best way to do it, as I don't know ruby all that well.