Bug 1389216

Summary:	Provisioning fails with RHV 4.0
Product:	Red Hat CloudForms Management Engine	Reporter:	lkerner
Component:	Provisioning	Assignee:	Oved Ourfali <oourfali>
Status:	CLOSED DUPLICATE	QA Contact:	Dave Johnson <dajohnso>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.7.0	CC:	gblomqui, jhardy, lkerner, obarenbo
Target Milestone:	GA
Target Release:	cfme-future
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	rhev
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-27 14:31:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	RHEVM	Target Upstream Version:
Embargoed:

Description lkerner 2016-10-27 08:24:59 UTC

Description of problem:
Template based provisioning fails for RHV 4 when VMs are provisioned from both Lifecycle->Provision VM and service catalogs. 

Version-Release number of selected component (if applicable):
Version 5.7.0.7-beta1.20161025153249_9376fbd 

How reproducible:
Always

Steps to Reproduce:
1. Add RHV 4 as a provider in CloudForms.
2. Do template based provisioning from either Lifecycle->Provision VM or service catalogs.
3. Tail evm.log,automation.log,rhevm.log, and open Web UI and view error

Actual results:
In the web UI, you will see:
Step [CheckProvisioned] Status [[Ovirt::MissingResourceError]: Ovirt::MissingResourceError] Message [[Ovirt::MissingResourceError]: Ovirt::MissingResourceError]


Expected results:
A vm to be provisioned successfully either by  Lifecycle->Provision VM or service catalogs.

Additional info:

Comment 2 Oved Ourfali 2016-10-27 14:13:21 UTC

What RHV version are you working?
We had issues that were fixed in 4.0.4.

Comment 3 lkerner 2016-10-27 14:24:46 UTC

RHV version 4.0.2.6-0.1.el7ev

Comment 5 Oved Ourfali 2016-10-27 14:31:20 UTC

Seems like it is a duplicate.
Please re-test with RHV 4.0.4.
Re-open if it doesn't work.

*** This bug has been marked as a duplicate of bug 1353720 ***