Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1332317 - Continuous queuing of EMS Refresh for VMWare Provider
Continuous queuing of EMS Refresh for VMWare Provider
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
5.4.0
Unspecified Unspecified
urgent Severity urgent
: GA
: 5.6.0
Assigned To: Adam Grare
Alex Newman
ems_refresh:vmware
: ZStream
Depends On:
Blocks: 1332665
  Show dependency treegraph
 
Reported: 2016-05-02 18:27 EDT by Jared Deubel
Modified: 2016-08-26 10:49 EDT (History)
10 users (show)

See Also:
Fixed In Version: 5.6.0.6
Doc Type: Bug Fix
Doc Text:
In the previous version of CloudForms Management Engine, EMS refreshes happened continuously on several providers. As a result, it broke or slowed provisioning down significantly. When the VimBroker terminated the connection it fired off a MiqVimRemoved event. The VimBrokerWorker was responding to this event by automatically re-connecting to that EMS. With this fix, instead it will now check the list of EMSs it is supposed to be connected to before re-connecting.
Story Points: ---
Clone Of:
: 1332665 (view as bug list)
Environment:
Last Closed: 2016-06-29 11:56:38 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)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 14:50:04 EDT

  None (edit)
Comment 8 CFME Bot 2016-05-10 00:10:46 EDT
New commit detected on ManageIQ/manageiq/master:
https://github.com/ManageIQ/manageiq/commit/4b534cb6af3aea69800b1023c570db39866107f9

commit 4b534cb6af3aea69800b1023c570db39866107f9
Author:     Adam Grare <agrare@redhat.com>
AuthorDate: Mon May 9 11:24:30 2016 -0400
Commit:     Adam Grare <agrare@redhat.com>
CommitDate: Mon May 9 15:36:07 2016 -0400

    Fix continuous refresh for inactive connection
    
    If a VimBroker connection is opened for an EMS that is not in
    the server's zone the VimBrokerWorker terminates the connection.
    
    When the VimBroker terminates the connection it fires off a
    MiqVimRemoved event.  The VimBrokerWorker was responding to
    this event by automatically re-connecting to that EMS.  Instead
    it should check the list of EMSs it is supposed to be connected
    to before re-connecting.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1332317

 app/models/miq_vim_broker_worker/runner.rb | 5 +++++
 1 file changed, 5 insertions(+)
Comment 11 CFME Bot 2016-05-12 11:07:22 EDT
New commit detected on cfme/5.5.z:
https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=83e1219679a13384c7cfb5ba926c6e0f36ee25d3

commit 83e1219679a13384c7cfb5ba926c6e0f36ee25d3
Author:     Adam Grare <agrare@redhat.com>
AuthorDate: Mon May 9 11:24:30 2016 -0400
Commit:     Adam Grare <agrare@redhat.com>
CommitDate: Tue May 10 08:01:55 2016 -0400

    Fix continuous refresh for inactive connection
    
    If a VimBroker connection is opened for an EMS that is not in
    the server's zone the VimBrokerWorker terminates the connection.
    
    When the VimBroker terminates the connection it fires off a
    MiqVimRemoved event.  The VimBrokerWorker was responding to
    this event by automatically re-connecting to that EMS.  Instead
    it should check the list of EMSs it is supposed to be connected
    to before re-connecting.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1332317

 app/models/miq_vim_broker_worker/runner.rb | 5 +++++
 1 file changed, 5 insertions(+)
Comment 14 errata-xmlrpc 2016-06-29 11:56:38 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:1348

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