Bug 1647286

Summary: overcloud deploy does not report cause of workflow failures to operator
Product: Red Hat OpenStack Reporter: Lars Kellogg-Stedman <lars>
Component: openstack-heatAssignee: Zane Bitter <zbitter>
Status: CLOSED ERRATA QA Contact: Artem Hrechanychenko <ahrechan>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: dbecker, emacchi, mburns, morazi, sbaker, shardy, slinaber
Target Milestone: z5Keywords: Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-heat-10.0.2-4.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1652696 (view as bug list) Environment:
Last Closed: 2019-03-14 13:50:23 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:
Embargoed:

Description Lars Kellogg-Stedman 2018-11-07 03:46:27 UTC
When a Mistral workflow fails during the overcloud deployment, the error is reported to the operator like this:

    overcloud.AllNodesDeploySteps.WorkflowTasks_Step5_Execution:
      resource_type: OS::TripleO::WorkflowSteps
      physical_resource_id: 3a0b5696-8f20-4d05-9222-0b9a7d763fc6
      status: CREATE_FAILED
      status_reason: |
        resources.WorkflowTasks_Step5_Execution: ERROR
    Heat Stack update failed.
    Heat Stack update failed.

This doesn't provide the operator with any information about the cause of the failure.  This is generally reported in mistral logs (engine.log, execution.log).  These failures should be collected by the mistral api, if they're not already, and then communicated to the operator.

Comment 1 Steve Baker 2018-11-19 21:46:23 UTC
Thomas, you may have the unique skills to improve the error path feedback from heat->mistral->user, let us know if you can take this bug.

Comment 10 errata-xmlrpc 2019-03-14 13:50:23 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/RHBA-2019:0563