Skip to content
This repository has been archived by the owner on Dec 12, 2019. It is now read-only.

Box fails to provision: template error while templating string #365

Open
MrDaleSmith opened this issue Jul 1, 2016 · 8 comments
Open

Box fails to provision: template error while templating string #365

MrDaleSmith opened this issue Jul 1, 2016 · 8 comments
Labels

Comments

@MrDaleSmith
Copy link

With the latest release of VLAD, I'm getting the error -

TASK: [get current Vlad version] **********************************************
fatal: [192.168.100.100] => Failed to template {% if [my base path]/vlad/vlad_guts %} True {% else %} False {% endif %}: template error while templating string: unexpected '/'

If I remove the changes in c7f9c91, specifically -

- name: set local inventory dir variable
  set_fact:
    inventory_dir: "/vagrant/"
  when: inventory_dir == false and vlad_running_local == false

and

  when: inventory_dir

from the site.yml, then I can get the box up.

@MrDaleSmith
Copy link
Author

Seems to be the
when: inventory_dir
that's causing the problem: removing it also allows the box to go up.

@philipnorton42
Copy link
Contributor

Very strange. I always do a full provision before releasing a new version just in case and this error wasn't there. Just did a test provision now to test and it all worked.
What version of Ansible are you using? Maybe it's a version thing?

@MrDaleSmith
Copy link
Author

ansible 1.9.2

@philipnorton42
Copy link
Contributor

That might be it. I'm running Ansible 2.0.0.1.
Are you able to update your rig?
In the meantime it might be worth adding more version requirements to Vlad to stop this sort of thing.

@MrDaleSmith
Copy link
Author

Sounds likely: I can't upgrade my ansible because I'm hitting an error with OPENSSL that I can't seem to find a workaround for: I made the stupid mistake up upgrading OSX last month and have regretted it ever since. But I'd guess the version is the cause.

@philipnorton42
Copy link
Contributor

I'm sure I had the same problem when I upgraded. Can't remember how I got around it now... :(
Let me know how you get on though!

@MrDaleSmith
Copy link
Author

It was the cryptography dependency that was failing: fixed it with the approach in http://masnun.com/2015/12/01/fixing-fatal-error-opensslaes-h-file-not-found-on-os-x.html

No issues provisioning in Ansible 2.1.0, so yeah looks like it needs an update the the minimum Ansible version requirement.

@philipnorton42
Copy link
Contributor

Cool. Thanks for clarifying :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants