AnsibleUndefinedVariable bootstrap

Bug #1674649 reported by Thomas O'Neill
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bifrost
Fix Released
Undecided
Pavlo Shchelokovskyy

Bug Description

When running

ansible-playbook -vvvv -i inventory/target install.yaml -e cleaning=false -e ansible_become=true

I'm getting the following error:

fatal: [127.0.0.1]: FAILED! => {"changed": false, "failed": true, "invocation": {"module_args": {"dest": "~user/.config/openstack/clouds.yaml", "mode": 384, "owner": "user", "src": "clouds.yaml.j2"}, "module_name": "template"}, "msg": "AnsibleUndefinedVariable: {u'bifrost': {u'config_project_name': u'baremetal', u'config_auth_url': u'{{ keystone.bootstrap.public_url }}', u'config_region_name': u'{{ keystone.bootstrap.region_name }}', u'config_username': u'{{ ironic.keystone.default_username }}', u'config_password': u'{{ ironic.keystone.default_password }}'}, u'bifrost-admin': {u'config_project_name': u'{{ keystone.bootstrap.project_name }}', u'config_auth_url': u'{{ keystone.bootstrap.public_url }}', u'config_region_name': u'{{ keystone.bootstrap.region_name }}', u'config_username': u'{{ keystone.bootstrap.username }}', u'config_password': u'{{ ironic.bootstrap.password }}'}}: 'dict object' has no attribute 'bootstrap'"}

description: updated
Revision history for this message
Thomas O'Neill (tomatopeel) wrote :

Also ran it with the command-line specified in the docs (using -K instead of -e ansible_become=true) and hitting the same error.

Changed in bifrost:
assignee: nobody → Pavlo Shchelokovskyy (pshchelo)
Revision history for this message
Thomas O'Neill (tomatopeel) wrote :

This isn't an issue with commit 7164cbfbd85b93e89fc0036a2d7c6428bcf4311e which is just prior to https://review.openstack.org/#/c/444820

Changed in bifrost:
assignee: Pavlo Shchelokovskyy (pshchelo) → nobody
Revision history for this message
Pavlo Shchelokovskyy (pshchelo) wrote :

I've found the root cause (actually my bad :) ), fix is on review https://review.openstack.org/#/c/449125/

This however highlights a problem with bifrost testing - we basically are only testing roles, but not the playbooks we advise users to use.

Ideally we should should somehow just include the install.yaml (and other playbooks) into the test-bifrost.yaml one to actually test them on gates.

Changed in bifrost:
assignee: nobody → Pavlo Shchelokovskyy (pshchelo)
status: New → In Progress
Revision history for this message
Pavlo Shchelokovskyy (pshchelo) wrote :

The patch is merged to master(Pike) [0], backport to stable/ocata which is also affected is also proposed [1]

[0] https://review.openstack.org/#/c/449125/
[1] https://review.openstack.org/#/c/462683

Changed in bifrost:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/bifrost 4.0.0

This issue was fixed in the openstack/bifrost 4.0.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/bifrost 3.1.1

This issue was fixed in the openstack/bifrost 3.1.1 release.

Dmitry Tantsur (divius)
Changed in bifrost:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.