Issues running foundation playbook without custom user variables

[James Denton]

Installing 12.0.8 on a 5-node cluster. On the deploy host, an error is encountered when running the setup-hosts.yml playbook and no changes to the default user_variables.yml file:

root@infra01:/opt/openstack-ansible/playbooks# openstack-ansible setup-hosts.yml
Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml "
ERROR: failed to combine variables, expected dicts but got a 'dict' and a 'NoneType'

To resolve this, I had to uncomment at least one option even though it is a default option. In this case, I uncommented the following line:

- # glance_default_store: file
+ glance_default_store: file

Rerunning the playbook at this point allowed it to proceed:

root@infra01:/opt/openstack-ansible/playbooks# openstack-ansible setup-hosts.yml
Variable files: "-e @/etc/openstack_deploy/user_secrets.yml -e @/etc/openstack_deploy/user_variables.yml "

PLAY [Basic host setup] *******************************************************

GATHERING FACTS ***************************************************************
ok: [infra01]
ok: [infra02]
ok: [compute01]
ok: [infra03]
ok: [compute02]

...

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/301906
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=bb61cc02afab66ab8965ced004bdf138b90c2ab6
Submitter: Jenkins
Branch: master

commit bb61cc02afab66ab8965ced004bdf138b90c2ab6
Author: Hector I Gonzalez <email address hidden>
Date: Tue Apr 5 15:27:35 2016 -0500

    Add debug and verbose to user variables

    Issue with ansible 1.9.x, if there is no custom user variables
    it will complain. Working around adding this verbose and debug
    variables uncommented.

    Change-Id: I5db9424e5f4421f9d0990baf28071f73d52d6fcd
    Closes-bug: 1563655

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/openstack-ansible 14.0.0.0b1 development milestone.

[Doug Hellmann (doug-hellmann)]

This issue was fixed in the openstack/openstack-ansible 14.0.0.0b2 development milestone.