Red Hat Bugzilla – Bug 1580547
tripleo-ansible-inventory returns {} when creating the ansible inventory
Last modified: 2018-08-29 12:37:24 EDT
If tripleo-ansible-inventory returns empty, the script should fail and display an error message for the users to fix the plan or stack name before continuing. Reproducible: 100% How to reproduce: Run: tripleo-ansible-inventory --stack overcloasdfud Expected result: Error showing that the inventory is empty Actual result: '{}' it finish with a status code of 0 instead of 1
This bug is marked for inclusion in the errata but does not currently contain draft documentation text. To ensure the timely release of this advisory please provide draft documentation text for this bug as soon as possible. If you do not think this bug requires errata documentation, set the requires_doc_text flag to "-". To add draft documentation text: * Select the documentation type from the "Doc Type" drop down field. * A template will be provided in the "Doc Text" field based on the "Doc Type" value selected. Enter draft text in the "Doc Text" field.
This change is causing a regression in validation and has already been reverted in tripleo-validations master branch. I addes a backport patch of the revert: https://review.openstack.org/#/c/596684/ As discussed with Carlos Camacho, a follow up patch should address this issue in a slightly different way that leaves the inventory intact if there is no overcloud deployed. The initial solution made the inventory exit with an error if there was no overcloud deployed, but validations need an inventory with at least the undercloud host info to run pre-deployment validations.
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-2018:2574