Read group_vars/all.yml in each nested Ansible execution in ci playbooks #3438
Conversation
Some of the CI jobs, even when ansible-playbook execution is done from ci-framework dir, does not read group_vars/all.yml variable file. That's because the playbook execution require to have symlink to the group_vars in the playbook dir. Until we still have nested ansible execution available in ci-framework, we should read the all.yml file using ansible extra vars parameters instead of relay that there should be symlink done in this dir. Signed-off-by: Daniel Pawlik <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/c7e454eb02ab45a295198b43ac9f0d4c ✔️ openstack-k8s-operators-content-provider SUCCESS in 1h 39m 16s |
|
recheck |
|
/lgtm with a depends-on to this PR the previously kuttl job in openstack-k8s-operators/nova-operator#1025 passed. |
3 participants
Some of the CI jobs, even when ansible-playbook execution is done from ci-framework dir, does not read group_vars/all.yml variable file. That's because the playbook execution require to have symlink to the group_vars in the playbook dir.
Until we still have nested ansible execution available in ci-framework, we should read the all.yml file using ansible extra vars parameters instead of relay that there should be symlink done in this dir.