Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

topology_output_file requires .yaml due to update to jinja2 2.8 #102

Closed
herlo opened this issue Nov 16, 2016 · 1 comment
Closed

topology_output_file requires .yaml due to update to jinja2 2.8 #102

herlo opened this issue Nov 16, 2016 · 1 comment

Comments

@herlo
Copy link
Contributor

herlo commented Nov 16, 2016

Because we updated to jinja2 2.8, ansible expects .yaml, .yml, or .json extensions for files that are being processed internally. Thus, calling linch-pin without topology_output_file=somevalue.yaml will result in a file that ends in .output.

Here's an example of the error from jenkins: https://ci.centos.org/job/paas-bfs-origin-0-test-matrix/PYTHON=system-CPython-2.7,TOPOLOGY=duffy_3node_cluster,nodes=paas-sig-ci-slave01/1/console

16:01:44 fatal: [localhost]: FAILED! => {"ansible_facts": {}, "changed": false, "failed": true, "message": "/home/sig-paas/workspace/paas-bfs-origin-0-test-matrix/PYTHON/system-CPython-2.7/TOPOLOGY/duffy_3node_cluster/nodes/paas-sig-ci-slave01/linch-pin/outputs/duffy_3node_cluster.output does not have a valid extension: yaml, yml, json"}

@herlo herlo added the bug label Nov 16, 2016
@herlo herlo self-assigned this Nov 16, 2016
@herlo
Copy link
Contributor Author

herlo commented Nov 16, 2016

#104 provided the complete fix. Thanks @arilivigni

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Development

No branches or pull requests

1 participant