Bug 1332512

Summary:	MIQ(MiqProvisionVmware#provision_error) [[Handsoap::Fault]: Handsoap::Fault { :code => 'ServerFaultCode', :reason => 'The object has already been deleted or has not been completely created' }]
Product:	Red Hat CloudForms Management Engine	Reporter:	Sachin <sacpatil>
Component:	Provisioning	Assignee:	Greg McCullough <gmccullo>
Status:	CLOSED NOTABUG	QA Contact:	Dave Johnson <dajohnso>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.4.0	CC:	jhardy, jocarter, obarenbo, sacpatil, thenness
Target Milestone:	GA
Target Release:	5.6.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-06 20:00:02 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	Inquiry
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Sachin 2016-05-03 11:15:49 UTC

Description of problem:

High CPU usage during provisioning. Issue is not consistent and can't be reproducible. 

Handsoap(Ruby gem) throws error with reason: "The object has already been deleted or has not been completely created".
(The error is related to VSphere)


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

5.4.5.2.20160315175001_800759c


How reproducible:

This is occasional.


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:

Should not get any handsoap errors

Additional info:

May be the error is related to 

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1039326

Comment 2 Greg McCullough 2016-05-03 18:45:42 UTC

Sachin - Please validate if this is a duplicate of bug 1280402?

See https://bugzilla.redhat.com/show_bug.cgi?id=1280402#c3

Comment 3 Sachin 2016-05-04 05:29:31 UTC

Hi Greg,

Even though the scenarios may be different, the point to notice here is VSphere.. while provisioning causes the error. Which is eventually caught by HandSoap.
Comment in the BZ 1280402 say that "manually refreshed dc-vcenter via the GUI - WORKED". I strongly feel that this is not bug in CFME but occurs via VSphere.