Bug 1389216 - Provisioning fails with RHV 4.0
Summary: Provisioning fails with RHV 4.0
Keywords:
Status: CLOSED DUPLICATE of bug 1353720
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning
Version: 5.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: cfme-future
Assignee: Oved Ourfali
QA Contact: Dave Johnson
URL:
Whiteboard: rhev
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-27 08:24 UTC by lkerner
Modified: 2016-11-01 04:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-27 14:31:20 UTC
Category: ---
Cloudforms Team: RHEVM
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.