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

Bug #1707948 reported by James Slagle on 2017-08-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
paunch
High
James Slagle
tripleo
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
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)

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

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  Edit
Everyone can see this information.

Other bug subscribers