Description of problem: One of the error messages is misleading say that we should look at '/var/log/mistral/package_update.log'. This file path on the Undercloud is actually '/var/log/containers/mistral/package_update.log'. There might not be much we can do here since it's the Mistral service in the container only being aware of the file system that is in itself (and not aware of the bind mounts). For customers, this could be confusing. Version-Release number of selected component (if applicable): RHOSP 13z12 to RHOSP 16.1 How reproducible: 100% Steps to Reproduce: 1. Follow the documentation to FFU but use pre-deployed nodes. 1a. https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1-beta/html-single/framework_for_upgrades_13_to_16.1/index?lb_target=preview 2. Upgrade an Overcloud node that does NOT have the updated RHOSP 16 repositories setup yet. 2a. openstack overcloud upgrade run --tags system_upgrade --limit overclou-controller-0 Actual results: $ openstack overcloud upgrade run --tags system_upgrade --limit overclou-controller-0 2020-06-15 12:37:46.622 309427 ERROR openstack [-] Update failed with: Ansible failed, check log at /var/log/mistral/package_update.log.: RuntimeError: Update failed with: Ansible failed, check log at /var/log/mistral/package_update.log. Expected results: check log at /var/log/containers/mistral/package_update.log Additional info: Ignore the actual error. We had to update the repositories used by the pre-provisioned/deployed servers first.
found a correct log entry on failed job 2020-07-17 17:34:44 | Ansible failed, check log at /var/log/containers/mistral/package_update.log.
If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text. If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
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/RHBA-2020:3148