Created attachment 1489062 [details] ansible-playbook run logs Description of problem: When trying to perform a "dry-run" on config download playbooks, check fails on the task :TASK [set is_bootstrap_node fact] TASK [set is_bootstrap_node fact] ********************************************************************************************************************************************************************************* fatal: [controller-2]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'\n\nThe error appears to have been in '/home/stack/cd-overcloud/ControllerOpenstack/host_prep_tasks.yaml': line 290, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n register: bootstrap_node\n - name: set is_bootstrap_node fact\n ^ here\n"} fatal: [controller-1]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'\n\nThe error appears to have been in '/home/stack/cd-overcloud/ControllerOpenstack/host_prep_tasks.yaml': line 290, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n register: bootstrap_node\n - name: set is_bootstrap_node fact\n ^ here\n"} fatal: [controller-0]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'\n\nThe error appears to have been in '/home/stack/cd-overcloud/ControllerOpenstack/host_prep_tasks.yaml': line 290, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n register: bootstrap_node\n - name: set is_bootstrap_node fact\n ^ here\n"} Version-Release number of selected component (if applicable): openstack-tripleo-common-9.3.1-0.20180920204842.el7ost.noarch How reproducible: Steps to Reproduce: 1. Install undercloud 2. Create stack with openstack overcloud deploy --stack-only 3. Generate config download files with openstack overcloud config download --config-dir cd-overcloud --name overcloud 4. Generate ansible inventory 5. Run ansible with --check option Actual results: TASK [set is_bootstrap_node fact] ********************************************************************************************************************************************************************************* fatal: [controller-2]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'\n\nThe error appears to have been in '/home/stack/cd-overcloud/ControllerOpenstack/host_prep_tasks.yaml': line 290, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n register: bootstrap_node\n - name: set is_bootstrap_node fact\n ^ here\n"} fatal: [controller-1]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'\n\nThe error appears to have been in '/home/stack/cd-overcloud/ControllerOpenstack/host_prep_tasks.yaml': line 290, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n register: bootstrap_node\n - name: set is_bootstrap_node fact\n ^ here\n"} fatal: [controller-0]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'dict object' has no attribute 'stdout'\n\nThe error appears to have been in '/home/stack/cd-overcloud/ControllerOpenstack/host_prep_tasks.yaml': line 290, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n register: bootstrap_node\n - name: set is_bootstrap_node fact\n ^ here\n"} Expected results: Check run completes successfully Additional info:
Verified on puddle 2018-10-10.3 2018-10-18 11:33:07,568 p=196580 u=stack | TASK [set is_bootstrap_node fact] ************************************************************************************************************************************************************************************************ 2018-10-18 11:33:07,664 p=196580 u=stack | ok: [controller-2] 2018-10-18 11:33:07,696 p=196580 u=stack | ok: [controller-1] 2018-10-18 11:33:07,697 p=196580 u=stack | skipping: [compute-1] 2018-10-18 11:33:07,697 p=196580 u=stack | ok: [controller-0] 2018-10-18 11:33:07,709 p=196580 u=stack | skipping: [compute-0] Task passes check successfully
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-2019:0045