Bug 1412289

Summary: Generate notification for Service Provisioning error in automate
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: AutomateAssignee: William Fitzgerald <wfitzger>
Status: CLOSED ERRATA QA Contact: Milan Falešník <mfalesni>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 5.7.0CC: jhardy, mkanoor, obarenbo, tfitzger
Target Milestone: GAKeywords: ZStream
Target Release: 5.7.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.7.1.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1411990 Environment:
Last Closed: 2017-02-27 19:21:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1411990    
Bug Blocks:    

Comment 2 CFME Bot 2017-01-11 21:30:54 UTC
New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/995e2fd74a9f4d0401757bfcc97b942ade05ae5e

commit 995e2fd74a9f4d0401757bfcc97b942ade05ae5e
Author:     Madhu Kanoor <mkanoor>
AuthorDate: Thu Dec 15 14:48:23 2016 -0500
Commit:     Satoe Imaishi <simaishi>
CommitDate: Wed Jan 11 16:29:35 2017 -0500

    Merge pull request #12306 from billfitzgerald0120/notify_service
    
    Automate - Notification for Service Provisioning error.
    (cherry picked from commit e68e228816a2a28f8f53f76ec305fdc6ad028439)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1412289

 .../__methods__/update_serviceprovision_status.rb          |  5 +++++
 .../update_service_provision_status_orchestration_spec.rb  | 14 ++++++++++++++
 2 files changed, 19 insertions(+)

Comment 3 Milan Falešník 2017-01-25 15:26:32 UTC
Verified in 5.7.1.0 against 5.7.0.17.

When tweaking the service automate model to fail, it throws a notification about it.

Comment 5 errata-xmlrpc 2017-02-27 19:21:24 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://rhn.redhat.com/errata/RHSA-2017-0320.html