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

Bug 1803331

Summary:	[OSP16] Heat stack output is silenced
Product:	Red Hat OpenStack	Reporter:	Michele Baldessari <michele>
Component:	python-tripleoclient	Assignee:	Alex Schultz <aschultz>
Status:	CLOSED ERRATA	QA Contact:	Sasha Smolyak <ssmolyak>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.0 (Train)	CC:	cjeanner, emacchi, hbrock, jschluet, jslagle, mburns, mgarciac, satmakur
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-tripleoclient-12.3.2-0.20200218225228.4c2ca96.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-14 12:15:31 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 Michele Baldessari 2020-02-15 09:55:27 UTC

Description of problem:
In latest puddles the heat stack output has disappeared, so there is no visual feedback as to what is going on with heat during a deployment (the ansible bits afterwards are fine).

A brief chat with Rabi and Cedric pointed me to https://review.opendev.org/#/c/707349/, which I backported. Today I started testing it and I still see no output even though I applied that review in my env, so likely something more is needed here?

Comment 1 Michele Baldessari 2020-02-16 07:39:28 UTC

*** Bug 1803423 has been marked as a duplicate of this bug. ***

Comment 2 Alex Schultz 2020-02-17 16:04:43 UTC

The reported issue is actually with the overcloud which was caused by a backport of https://review.opendev.org/#/c/703503/

Comment 9 errata-xmlrpc 2020-05-14 12:15:31 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-2020:2114