Bug 1267375 – Lifecycle provisioning of VMs fails with Unexpected Error

Bug 1267375 - Lifecycle provisioning of VMs fails with Unexpected Error

Summary:	Lifecycle provisioning of VMs fails with Unexpected Error

Status:	CLOSED UPSTREAM

Aliases:	None

Product:	Red Hat CloudForms Management Engine
Classification:	Red Hat
Component:	Provisioning (Show other bugs)
Sub Component:
Version:	5.5.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	GA
Target Release:	5.5.0
Assigned To:	Greg McCullough
QA Contact:	Dave Johnson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2015-09-29 16:05 EDT by bmorriso
Modified:	2015-11-11 15:21 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2015-09-29 16:29:04 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description bmorriso 2015-09-29 16:05:48 EDT

Description of problem:
When submitting a lifecycle provisioning request to provision a VM, an "Unexpected Error" page is returned, and the VM is not provisioned 

Version-Release number of selected component (if applicable):
5.5.0.2-alpha1.1.20150923081748_2e8e945

How reproducible:
always

Steps to Reproduce:
1. On an appliance with an infrastructure provider present, navigate to infrastructure>VMs
2. Select lifecycle>Provision VMs
3. Select configuration options for VM and click "Submit"

Actual results:
Unexpected Error page appears with the error:

undefined method `make_request' for #<ManageIQ::Providers::Vmware::InfraManager::ProvisionWorkflow:0x0000000416d5d8> [vm_infra/pre_prov_continue]

Expected results:
The VM provisions

Additional info:

Comment 2 Greg McCullough 2015-09-29 16:29:04 EDT

This bug was introduced in https://github.com/ManageIQ/manageiq/pull/4332 and fixed a day later in PR https://github.com/ManageIQ/manageiq/pull/4494.

Note You need to log in before you can comment on or make changes to this bug.