Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
First Last Prev Next    This bug is not in your last search results.
Bug 1322002 - Events from vSphere stop working shortly after an appliance reboot (20-30 minute)
Events from vSphere stop working shortly after an appliance reboot (20-30 min...
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
5.4.0
Unspecified Unspecified
high Severity high
: GA
: 5.5.4
Assigned To: Adam Grare
Nandini Chandra
event
: ZStream
Depends On: 1316282 1322004
Blocks:
  Show dependency tree / graph
 
Reported: 2016-03-29 10:29 EDT by John Prause
Modified: 2017-08-29 21:20 EDT (History)
10 users (show)

See Also:
Fixed In Version: 5.5.4.0
Doc Type: Bug Fix
Doc Text:
Previously, VMware power events and provisioning performed directly in vCenter stopped being received by the CloudForms appliance shortly after an appliance reboot (20-30 minutes). This occurred because using HTTP timeout with the WaitForUpdates call on a vSphere provider caused calls to hang eventually. VMware added the new WaitForUpdatesEx method to vSphere 4.1 to address this issue, which has been updated in this version of CloudForms. The maxWait option in WaitForUpdatesEx controls how long to block in WaitForUpdatesEx without timing out the connection.
Story Points: ---
Clone Of: 1316282
Environment:
Last Closed: 2016-05-31 09:41:48 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.)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1101 normal SHIPPED_LIVE CFME 5.5.4 bug fixes and enhancement update 2016-05-31 13:40:10 EDT

  None (edit)
Comment 2 CFME Bot 2016-04-25 12:56:04 EDT 
New commit detected on cfme/5.5.z:
https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=b4da1f3b3a5330b1cc8d53e20e966b8958e27313

commit b4da1f3b3a5330b1cc8d53e20e966b8958e27313
Merge: ae9ba6f 90d3c18
Author:     Greg Blomquist <gblomqui@redhat.com>
AuthorDate: Mon Apr 25 11:10:42 2016 -0400
Commit:     Greg Blomquist <gblomqui@redhat.com>
CommitDate: Mon Apr 25 11:10:42 2016 -0400

    Merge branch 'bz_1322002_5.5.z_vsphere_events' into '5.5.z'
    
    Bz 1322002 5.5.z vsphere events
    
    Move to a non-deprecated method to get VMware events.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1322002
    
    See merge request !873

 .../vmware/infra_manager/event_catcher/runner.rb   |  3 ++-
 config/vmdb.tmpl.yml                               |  1 +
 gems/pending/VMwareWebService/DMiqVim.rb           |  3 ++-
 gems/pending/VMwareWebService/MiqVimCoreUpdater.rb | 11 +++++++----
 .../pending/VMwareWebService/MiqVimEventMonitor.rb |  7 +++++--
 gems/pending/VMwareWebService/MiqVimUpdate.rb      |  6 ++++--
 gems/pending/VMwareWebService/VimService.rb        | 23 ++++++++++++++++++++++
 7 files changed, 44 insertions(+), 10 deletions(-)
Comment 4 Nandini Chandra 2016-05-05 17:58:03 EDT 
I haven't been able to reproduce this issue.

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

Verified that the code is present.
Comment 6 errata-xmlrpc 2016-05-31 09:41:48 EDT 
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:1101
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.