using --start-at-task causes keystone resource management to fail

Bug #1913331 reported by Alex Schultz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Invalid
Medium
Alex Schultz

Bug Description

If you run the ansible deployment playbook using a --start-at-task that skips the global vars loading, the keystone resource tasks fail because keystone_resources is undefined. We should include a global var loading/check if keystone_resources is undefined.

2021-01-26 18:22:36.581518 | fa163eb6-0b6b-33ca-ae8e-0000000019db | TASK | Create Keystone Projects
2021-01-26 18:22:36.622582 | fa163eb6-0b6b-33ca-ae8e-0000000019db | FATAL | Create Keystone Projects | undercloud | error={"msg": "{{ keystone_resources }}: 'keystone_resources' is undefined"}

Revision history for this message
Alex Schultz (alex-schultz) wrote :
Changed in tripleo:
assignee: nobody → Alex Schultz (alex-schultz)
status: Triaged → In Progress
Changed in tripleo:
milestone: wallaby-2 → wallaby-3
Revision history for this message
Alex Schultz (alex-schultz) wrote :

This can be avoided by -e @global-vars.yaml when using --start-at-tasks

Changed in tripleo:
status: In Progress → Invalid
Revision history for this message
Alex Schultz (alex-schultz) wrote :
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.