tripleo

tripleoclient not logging image build output

Bug #1653768 reported by Ben Nemec
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Ben Nemec
tripleo pike-1 "pike-1"

Bug Description

If you run image builds using the new yaml method from tripleoclient you get no image build output. This is a pretty terrible user experience both because there is no indication that anything is happening while the image build is in progress and because if the image build fails there's no way to tell why.

Revision history for this message
Ben Nemec (bnemec) wrote :

Probably should have included this in the first place, but here's the output I got from trying to run a standalone image build:

[centos@undercloud ~]$ openstack overcloud image build --config-file /usr/share/openstack-tripleo-common/image-yaml/overcloud-images.yaml --config-file $OS_YAML
Command '['disk-image-create', '-a', 'amd64', '-o', './ironic-python-agent.qcow2', '-t', 'qcow2', '-p', 'python-hardware-detect,yum-plugin-priorities', '--min-tmpfs=5', 'centos7', 'ironic-agent', 'dynamic-login', 'element-manifest', 'network-gateway', 'enable-packages-install', 'pip-and-virtualenv-override', 'selinux-permissive']' returned non-zero exit status 1
[centos@undercloud ~]$

tags: added: tripleoclient
Changed in tripleo:
milestone: none → ocata-3
Dougal Matthews (d0ugal)
Changed in tripleo:
milestone: ocata-3 → pike-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (master)

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

Changed in tripleo:
assignee: nobody → Ben Nemec (bnemec)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

Reviewed: https://review.openstack.org/431075
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=484d08afea34f2c87ddc673722513a3108d7dec2
Submitter: Jenkins
Branch: master

commit 484d08afea34f2c87ddc673722513a3108d7dec2
Author: Ben Nemec <email address hidden>
Date: Wed Feb 8 17:11:08 2017 +0000

    Re-enable tee behavior for image builds

    The previous client-based image builds tee'd the output to both a
    log file and stdout. With the yaml-based image builds we lost that
    behavior, which makes for a bad user experience when the console
    just seems to sit there for 30 minutes while images build, with no
    feedback on what's going on. In addition, due to the default
    openstackclient logging configuration, we don't even see the info
    message telling the user which file contains the log output.

    This change uses the same method as the instack-undercloud
    _run_live_command method to tee the output to both the Python
    logger and the log file. It also ensures that our local logger is
    configured such that info level messages will be seen.

    Change-Id: I7e17a18a8bc170ea70955c87a84ca401cb44aa19
    Closes-Bug: 1653768
    Closes-Bug: 1646226

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

This issue was fixed in the openstack/tripleo-common 5.8.0 release.

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

Other bug subscribers

Remote bug watches

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