Hide Forgot
Description of problem: openstack stack failures list overcloud outputs the Ansible task output on a single line which makes it very difficult to read in order to debug the failure. Below is such an example: http://paste.openstack.org/show/615126/ We should format the task failure output so it is easy to read by a human operator in order to quickly spot what went wrong. Version-Release number of selected component (if applicable): puppet-tripleo-7.1.1-0.20170627224658.f99b72a.el7ost.noarch openstack-tripleo-common-containers-7.2.1-0.20170628001837.5a6423b.el7ost.noarch openstack-tripleo-heat-templates-7.0.0-0.20170628002128.el7ost.noarch openstack-tripleo-image-elements-7.0.0-0.20170607161959.401d861.el7ost.noarch python-tripleoclient-7.1.1-0.20170628001144.e4e66f7.el7ost.noarch openstack-tripleo-common-7.2.1-0.20170628001837.5a6423b.el7ost.noarch openstack-tripleo-validations-7.1.1-0.20170627224206.591a65f.el7ost.noarch openstack-tripleo-ui-7.1.1-0.20170627161345.68e8684.el7ost.noarch openstack-tripleo-puppet-elements-7.0.0-0.20170614005502.9285877.el7ost.noarch
Bogdan recently pushed a change upstream that should dramatically improve ansible logs readability: https://review.openstack.org/#/c/474269/
(In reply to Martin André from comment #1) > Bogdan recently pushed a change upstream that should dramatically improve > ansible logs readability: https://review.openstack.org/#/c/474269/ According to Jarda - If it's not in already by now , that would be RFE for osp13. Marius - Can you please retest with the patch ?
Re-reading the initial issue here this seems to be related to not liking the format of the Ansible output from the CLI. And not necessarily a containers specific issue. As such it is unclear to me that the patch Martin Andre linked in above would fix the issue. Alex: Not convinced this one belongs to the containers DFG. Will wait for feedback from QE before re-assigning.
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-2017:3462