Created attachment 1507454[details]
overcloud_scale_up.log
Description of problem:
When doing stack updates the entire plan content is output to stdout. This is recently introduced as it wasn't there before. Moreover it is not user friendly at all as it fills out the console with a lot of data not relevant to the user.
Version-Release number of selected component (if applicable):
python-tripleoclient-10.6.1-0.20181010222405.8c8f259.el7ost.noarch
How reproducible:
100%
Steps to Reproduce:
1. Deploy OSP14
2. Scale out with one additional compute
Actual results:
The plan content gets to stdout during scale out.
Expected results:
The plan content doesn't get to stdout.
Additional info:
Attaching an example.
Comment 1Artem Hrechanychenko
2018-11-20 19:40:15 UTC
Created attachment 1507456[details]
overcloud_install.log
that issue also appears when you do regular deployment also
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/RHEA-2019:0045
Created attachment 1507454 [details] overcloud_scale_up.log Description of problem: When doing stack updates the entire plan content is output to stdout. This is recently introduced as it wasn't there before. Moreover it is not user friendly at all as it fills out the console with a lot of data not relevant to the user. Version-Release number of selected component (if applicable): python-tripleoclient-10.6.1-0.20181010222405.8c8f259.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy OSP14 2. Scale out with one additional compute Actual results: The plan content gets to stdout during scale out. Expected results: The plan content doesn't get to stdout. Additional info: Attaching an example.