vagrant up failed

[davidemoro]

Hi,

all fine expect this error during vagrant up:

TASK: [symfony | Update app_dev.php] ****************************************** 
fatal: [default] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'private_interface' is undefined", 'failed': True}
fatal: [default] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'private_interface' is undefined", 'failed': True}

FATAL: all hosts have already failed -- aborting

PLAY RECAP ******************************************************************** 
           to retry, use: --limit @/home/davide/playbook.retry

default                    : ok=14   changed=10   unreachable=1    failed=0   

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

Am I doing something of wrong?

Thank you,

davide

[totophe]

Hi @davidemoro What are the versions of Vagrant/Ansible you are using? I just tried on my local machine, and it seems to run fine. I'm with OSX Yosemite, Vagrant 1.6.5 and Ansible 1.7.2 on a fresh system.

[davidemoro]

Hi @totophe,

my fault! Vagrant version too old, thank you.

After the installation should I expect a working hello world implemented with Symfony? I see a 502 page now.

Thank you very much

[totophe]

After the installation, you should be able to access it via http://192.168.100.100/app_dev.php although sometimes there is a permission issue with php-fpm socket that you might have to fix.

[davidemoro]

Fixed following this article:
http://www.nginxtips.com/php5-fpm-sock-failed-13-permission-denied-error/

I've fixed on my fork: https://github.com/davidemoro/symfony-vagrant-ansible
Can you review please? If it seems good for you I can create a pull request.

[totophe]

You can do a pull request :)

[tigitz]

Hey @totophe ,

I had to check the issue section about this specific problem. Could we find a way to update the master branch with a fix ? Seems like @davidemoro PR have some unrelated commits at the moment, should we try to clear it or make another PR ?

Thanks for your work, definately something that'll help me in my workflow.

[totophe]

Hi @tigitz

Sorry for late reply :-) So You can maybe propose another PR for it, but the solution should be to change everything to vagrant and not the opposit, IMHO.

What do you think ?

Br,

JCC