tripleo-heat-templates does not show docker error messages when running paunch

Bug #1707948 reported by James Slagle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
paunch
Fix Released
High
James Slagle
tripleo
Fix Released
High
James Slagle

Bug Description

paunch will only show the stderr from docker in a LOG.debug. If the command fails, we ought to show the stderr somewhere in the log, otherwise the user will never see what actually caused the error.

Changed in tripleo:
status: New → In Progress
importance: Undecided → High
assignee: nobody → James Slagle (james-slagle)
milestone: none → pike-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to paunch (master)

Fix proposed to branch: master
Review: https://review.openstack.org/489640

Changed in paunch:
assignee: nobody → Steve Baker (steve-stevebaker)
Changed in paunch:
assignee: Steve Baker (steve-stevebaker) → nobody
status: New → In Progress
importance: Undecided → High
assignee: nobody → James Slagle (james-slagle)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to paunch (master)

Reviewed: https://review.openstack.org/489640
Committed: https://git.openstack.org/cgit/openstack/paunch/commit/?id=64df79c70d4156da2bcc29eb18d12b0193414dc7
Submitter: Jenkins
Branch: master

commit 64df79c70d4156da2bcc29eb18d12b0193414dc7
Author: James Slagle <email address hidden>
Date: Tue Aug 1 11:42:20 2017 -0400

    Log stdout/stderr during error

    Paunch does not currently show stdout/stderr from the docker cmd when an
    error happens. Without this output, there is no way to tell what
    actually caused the container command to fail.

    Log the output with LOG.error if we get an unexpected return code so
    that the actual error is displayed to the user.

    Change-Id: I951cdf0cb2bfd87a22a239ff7522ab5bba9d6eb6
    Closes-Bug: #1707948

Changed in tripleo:
status: In Progress → Fix Released
Changed in paunch:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/paunch 1.5.0

This issue was fixed in the openstack/paunch 1.5.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.