https://github.com/ManageIQ/manageiq/pull/8551
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/4b534cb6af3aea69800b1023c570db39866107f9 commit 4b534cb6af3aea69800b1023c570db39866107f9 Author: Adam Grare <agrare> AuthorDate: Mon May 9 11:24:30 2016 -0400 Commit: Adam Grare <agrare> 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(+)
https://github.com/ManageIQ/manageiq/pull/7950
https://github.com/ManageIQ/manageiq/pull/8407
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> AuthorDate: Mon May 9 11:24:30 2016 -0400 Commit: Adam Grare <agrare> 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(+)
https://github.com/ManageIQ/manageiq/pull/8473
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