commit 56448dafeda8db1916b2a65fd19bd70c7e6ff176
Author: Ben Nemec <email address hidden>
Date: Wed Nov 22 17:09:13 2017 -0600
Swap the order of stdout and stderr in debug output
Generally this data is looked at because something failed, and in
that case the relevant error is likely to be at the end of stderr.
By concatenating the output stderr first and then stdout as we were
it is possible for the stderr to get lost entirely in the failures
list, and even if that doesn't happen it's best to output the
relevant error right at the end of the output where people will
see it. Previously it would be buried in the middle of the debug
output.
Closes-bug: #1743754
Change-Id: I952fd1af5778ade1eb6b0599d983f98cadeb7f6f
(cherry picked from commit 5595e7fc14430ee0636060afc82f909d4b3d04be)
Reviewed: https:/ /review. openstack. org/535326 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=56448dafeda 8db1916b2a65fd1 9bd70c7e6ff176
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 56448dafeda8db1 916b2a65fd19bd7 0c7e6ff176
Author: Ben Nemec <email address hidden>
Date: Wed Nov 22 17:09:13 2017 -0600
Swap the order of stdout and stderr in debug output
Generally this data is looked at because something failed, and in
that case the relevant error is likely to be at the end of stderr.
By concatenating the output stderr first and then stdout as we were
it is possible for the stderr to get lost entirely in the failures
list, and even if that doesn't happen it's best to output the
relevant error right at the end of the output where people will
see it. Previously it would be buried in the middle of the debug
output.
Closes-bug: #1743754
Change-Id: I952fd1af5778ad e1eb6b0599d983f 98cadeb7f6f 0636060afc82f90 9d4b3d04be)
(cherry picked from commit 5595e7fc14430ee