Bug 1552335

Summary: EventCatcher is not restarted when Nuage provider is updated
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ProvidersAssignee: Gregor Berginc <gregor.berginc>
Status: CLOSED ERRATA QA Contact: Gregor Berginc <gregor.berginc>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: bsorota, cpelland, gblomqui, izapolsk, jfrey, jhardy, mplesko, obarenbo, simaishi, smallamp
Target Milestone: GAKeywords: Reopened, ZStream
Target Release: 5.9.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.9.2.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1534460 Environment:
Last Closed: 2018-05-07 20:43:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Nuage Target Upstream Version:
Embargoed:
Bug Depends On: 1534460    
Bug Blocks:    

Comment 2 CFME Bot 2018-03-06 23:48:34 UTC 
New commit detected on ManageIQ/manageiq-providers-nuage/gaprindashvili:

https://github.com/ManageIQ/manageiq-providers-nuage/commit/fcdf577e65e6c8a06c802ad823bd75089482de5b
commit fcdf577e65e6c8a06c802ad823bd75089482de5b
Author:     Julian Cheal <julian.cheal>
AuthorDate: Tue Feb  6 09:22:59 2018 -0500
Commit:     Julian Cheal <julian.cheal>
CommitDate: Tue Feb  6 09:22:59 2018 -0500

    Merge pull request #65 from sasoc/restart-event-catcher-on-provider-update

    Add `stop_event_monitor_queue_on_change` method
    (cherry picked from commit d597f5d5e4ba3527ccedc8782c06594e36bb5aad)

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1552335

 app/models/manageiq/providers/nuage/manager_mixin.rb | 11 +
 1 file changed, 11 insertions(+)
Comment 3 Sudhir Mallamprabhakara 2018-04-27 02:45:40 UTC 
No Customer Case. QE unable to test. Closing.
Comment 6 errata-xmlrpc 2018-05-07 20:43:22 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/RHSA-2018:1328