Bug 1803331 - [OSP16] Heat stack output is silenced
Summary: [OSP16] Heat stack output is silenced
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-tripleoclient
Version: 16.0 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Alex Schultz
QA Contact: Sasha Smolyak
URL:
Whiteboard:
: 1803423 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-15 09:55 UTC by Michele Baldessari
Modified: 2020-05-14 12:16 UTC (History)
8 users (show)

Fixed In Version: python-tripleoclient-12.3.2-0.20200218225228.4c2ca96.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-14 12:15:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1863633 0 None None None 2020-02-17 16:07:00 UTC
OpenStack gerrit 708207 0 None MERGED Revert "Default to zero verbosity when using Ansible." 2021-02-05 15:07:32 UTC
Red Hat Product Errata RHBA-2020:2114 0 None None None 2020-05-14 12:16:01 UTC

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


Note You need to log in before you can comment on or make changes to this bug.