Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1652696

Summary:	overcloud deploy does not report cause of workflow failures to operator
Product:	Red Hat OpenStack	Reporter:	Thomas Hervé <therve>
Component:	openstack-heat	Assignee:	Zane Bitter <zbitter>
Status:	CLOSED ERRATA	QA Contact:	Ronnie Rasouli <rrasouli>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	14.0 (Rocky)	CC:	apetrich, dbecker, emacchi, lars, mariel, mburns, morazi, sasha, sbaker, shardy, slinaber
Target Milestone:	z1	Keywords:	Triaged, ZStream
Target Release:	14.0 (Rocky)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-heat-11.0.1-0.20181010161428.46aacab.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, the OS::Mistral::ExternalResource resource type did not report the text of any error in the execution of a Mistral workflow. This led to incomplete ERROR messages if a Mistral workflow failed. This fix adds the execution `state_info` content to the error message, which shows the reason for the workflow failure.	Story Points:	---
Clone Of:	1647286	Environment:
Last Closed:	2019-03-18 13:01:20 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 Thomas Hervé 2018-11-22 15:52:08 UTC

+++ This bug was initially created as a clone of Bug #1647286 +++

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.

--- Additional comment from Steve Baker on 2018-11-19 16:46:23 EST ---

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 5 errata-xmlrpc 2019-03-18 13:01:20 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:0589