Bug 1316282

Summary:	Events from vSphere stop working shortly after an appliance reboot (20-30 minute)
Product:	Red Hat CloudForms Management Engine	Reporter:	Jared Deubel <jdeubel>
Component:	Providers	Assignee:	Adam Grare <agrare>
Status:	CLOSED ERRATA	QA Contact:	Nandini Chandra <nachandr>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.4.0	CC:	agrare, gblomqui, jdeubel, jfrey, jhardy, jprause, mfeifer, nachandr, obarenbo
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	event
Fixed In Version:	5.6.0.1	Doc Type:	Bug Fix
Doc Text:	Previously, using HTTP timeout with the WaitForUpdates method caused calls to VMware vSphere to hang. Consequently, vSphere events stopped working 20-30 minutes after an appliance reboot. VMware vSphere 4.1 added the WaitForUpdatesEx method to address the issue of WaitForUpdates blocking processes for a long time. This CloudForms release contains WaitForUpdatesEx, which can be used with the maxWait property to configure blocking limits for WaitForUpdatesEx without needing to time out the connection.	Story Points:	---
Clone Of:
Clones:	1322002 1322004 (view as bug list)		Environment:
Last Closed:	2016-06-29 15:41:10 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:	1322002, 1322004

Description Jared Deubel 2016-03-09 21:29:52 UTC

Description of problem:

We are encountering an issue on CF 3.2 with catching events from VMware for provisioning performed outside CF directly in vCenter, and for power events.  

* vCenter 5.5 appliance on laptop.  Initially VmDeploy events are received for start and finish:

After the events stop we are still seeing property changes come in and the worker still running. 

Ongoing issue that is causing provisioning failures and Administration issues.

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

How reproducible:
100%

Comment 12 Nandini Chandra 2016-04-29 03:58:14 UTC

I haven't been able to reproduce this issue.

Marking this as VERIFIED since GSS has confirmed that the fix resolved the issue.

Comment 15 errata-xmlrpc 2016-06-29 15:41:10 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1348