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:
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
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.
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.
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.