Hide Forgot
Description of problem: FFU: openstack overcloud upgrade run outputs to stdout content which is not human readable. To give a brief example the following tasks output a huge amount of data which should be stored on a persistent location instead of stdout output: TASK [Upgrade Mysql database from the host] TASK [take new os-net-config parameters into account now] TASK [Update all packages] <= this one actually puts the entire output of yum update * in the Ansible task json output Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-8.0.2-4.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Run upgrade commands. Actual results: A lot of information which is not human readable. Expected results: stdout should reflect information relevant and readable by the user and point to the error in case of failure. The verbose logging should be stored on a persistent location that can be used for later debug purposes. Additional info: I believe this applies to all ffu/upgrade/updates. I am attaching such example from running openstack overcloud upgrade run --roles Controller --skip-tags validation.
Created attachment 1427901 [details] overcloud_upgrade_Controller.log
@Jirka, this BZ has been assigned to you during triage duty call. Please, feel free to reasign.
This is a cosmetic bug that we need to solve, but it does not affect the FFWD workflow, removing the blocker flag.
Output of ansible playbook is available in /var/log/mistral/package_update.log
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2086