Containers: config step output too big for Heat, failure reason can get trimmed away

[Jiří Stránský]

There was a relatively non-special-looking failure in the senario004 -- bug 1700082. Yet the output from that step was so huge (mostly Puppet logs), that the real cause of the issue at the beginning of the output got trimmed away, and `failures list --long` didn't contain helpful info at all.

Trimmed failures list:
http://logs.openstack.org/98/476698/1/experimental/gate-tripleo-ci-centos-7-scenario004-multinode-oooq-container/d9ca1b2/logs/undercloud/home/jenkins/failed_deployment_list.log.txt.gz

Actual error:
http://logs.openstack.org/98/476698/1/experimental/gate-tripleo-ci-centos-7-scenario004-multinode-oooq-container/d9ca1b2/logs/subnode-2/var/log/messages.txt.gz#_Jun_22_21_43_03

[Bogdan Dobrelya (bogdando)]

Let's just use logdest syslog everywhere we invoke puppet

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/474269
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=c011a34f5e84ffadb55e0a0583897ab59c5bd4da
Submitter: Jenkins
Branch: master

commit c011a34f5e84ffadb55e0a0583897ab59c5bd4da
Author: Bogdan Dobrelya <email address hidden>
Date: Fri Jun 9 18:03:50 2017 +0200

    Improve logs from ansible, puppet, docker-puppet.py

    * Debug ansible 'puppet apply' stderr joined stdout, split
      by lines.
    * Do 'puppet apply' w/o colors, logdest syslog, and given a wanted
      modulepath instead of the module puppet, that can't support those
      options.
    * Bind-mount syslog socket for docker-puppet.py to pass puppet logs
      to host OS syslog.
    * Fix logging handlers for multiprocess workers in docker-puppet.py.

    Related-bug: #1698172
    Closes-bug: #1700086

    Change-Id: I84112a836e968aa5c3596a6544e0392980529963
    Signed-off-by: Bogdan Dobrelya <email address hidden>

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 7.0.0.0b3 development milestone.