Bug 1339309

Summary: vms deployed in a multi-cluster rhevm environment are tied to the cluster of the template
Product: Red Hat CloudForms Management Engine Reporter: Felix Dewaleyne <fdewaley>
Component: ProvidersAssignee: Boriso <bodnopoz>
Status: CLOSED CURRENTRELEASE QA Contact: Ilanit Stein <istein>
Severity: high Docs Contact:
Priority: high    
Version: 5.5.0CC: cpelland, gblomqui, gmccullo, jfrey, jhardy, lavenel, masayag, obarenbo, oourfali, simaishi
Target Milestone: GAKeywords: FutureFeature, TestOnly, ZStream
Target Release: 5.7.0   
Hardware: All   
OS: All   
Whiteboard: rhevm
Fixed In Version: 5.7.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1354562 (view as bug list) Environment:
Last Closed: 2017-01-11 20:09:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1354562    

Description Felix Dewaleyne 2016-05-24 16:18:38 UTC
Description of problem:
In cloudforms 4.0, vms deployed in a multi-cluster rhevm environment are tied to the cluster of the template

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

How reproducible:
all the time

Steps to Reproduce:
1. deploy a rhevm environment with multiple clusters
2. deploy from templates using prov.set_cluster
3.

Actual results:
the prov.set_cluster is not honored

Expected results:
the prov.set_cluster is honored

Additional info:
workaround : use 

prov.set_option(:placement_cluster_id)

Comment 2 Loic Avenel 2016-06-15 18:03:56 UTC
I don't see this as RFE,  We are not aligning with RHEV fonctionallities. Customer cannot deploy VMs today because you cannot select Clusters you need. SA has to enforce cluster in Ruby to fix this issue. but provision instance is broken.

Comment 3 Boriso 2016-06-21 12:38:03 UTC
So after some emailing it seems there is a deeper problem here - on RHEVM the new VM can be created only in the same datacenter as the template. CFME does not know what a datacenter is.
So currently it does not even offer to choose any cluster except the one the template belongs to.
We need to decide what to do with this.

Comment 4 Ilanit Stein 2016-06-21 13:26:57 UTC
Some more details:

On RHEV 3.6, it is possible to create a VM from a template on the same data center, and have the VM's cluster, other than the template's cluster.

On CFME side, provision a VM, can be only to the template's cluster.

Comment 8 CFME Bot 2016-07-20 19:15:53 UTC
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/0251c83adf2e3417bb610ff44671cdbd157ffe85

commit 0251c83adf2e3417bb610ff44671cdbd157ffe85
Author:     borod108 <bodnopoz>
AuthorDate: Mon Jul 11 16:06:22 2016 +0300
Commit:     borod108 <bodnopoz>
CommitDate: Wed Jul 20 18:28:03 2016 +0300

    Changed allowed_host_obj override in rhevm provision_workflow
    
    Changing allowed_host_obj and allowed_datacenters override in redhat provision_workflow so that all
    hosts from same data center will be returned not only from same cluster.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1339309

 .../redhat/infra_manager/provision_workflow.rb     | 24 +++++++++++++++-------
 app/models/miq_request_workflow.rb                 |  8 ++++----
 2 files changed, 21 insertions(+), 11 deletions(-)

Comment 9 Ilanit Stein 2016-09-13 07:18:56 UTC
Tested on:

CFME 5.7.0.0.20160906172503_12f65cb
RHV-4.0.4.2-0.1.el7ev

Provision VM from template, in case there are more than one cluster,
now allow choosing in the Provision tab clusters other than the template cluster,
and provision request start,
but due to current provision bug 1374995, provision VM eventually fail.

Need to be retest once bug 1374995 resolved.

Comment 10 Ilanit Stein 2016-09-19 13:37:34 UTC
Verified on CFME-5.7.0.1.20160913164703_66caf07, along with adding the fix for bug 1374995.

VM provisioned from template successfully on a cluster, other than the template cluster, on the same datacenter. VM also started successfully.