| Summary: | Events from vSphere stop working shortly after an appliance reboot (20-30 minute) | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | John Prause <jprause> |
| 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, dajohnso, gblomqui, jdeubel, jfrey, jhardy, jprause, mfeifer, nachandr, obarenbo |
| Target Milestone: | GA | Keywords: | ZStream |
| Target Release: | 5.5.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | event | ||
| 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 13:41:48 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: | |
| Bug Depends On: | 1316282, 1322004 | ||
| Bug Blocks: | |||
|
Comment 2
CFME Bot
2016-04-25 16:56:04 UTC
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. 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 |