search

hashbangcode / vlad

Vlad - Vagrant LAMP Ansible Drupal
173 stars 53 forks source link

Provisioning fails on "test | default host is setup" #84

Closed philipnorton42 closed 10 years ago

philipnorton42 commented 10 years ago

I had error this earlier today and thought that it had been fixed by this commit:

https://bitbucket.org/philipnorton42/vlad/commits/2a6116f3b18d0d7e14d998379ad033c55ee9ac6d

TASK: [test | default host is setup] ****************************************** 
2014-09-09 14:45:24,834 p=18890 u=danbohea |  failed: [eti] => {"changed": false, "cmd": ["curl", "-I", "http://www.eti.local", "--resolve", "www.eti.local:127.0.0.1"], "delta": "0:00:35.195440", "end": "2014-09-09 13:45:18.893877", "failed": true, "failed_when_result": true, "rc": 6, "start": "2014-09-09 13:44:43.698437", "stdout_lines": []}

stderr: curl: (6) Couldn't resolve host 'www.eti.local'

But just now, even running latest dev including the above commit I just got the same error.

Commenting out that test entirely does seem to bypass it (obviously) and the site seems to be working just fine. Is this still a wonky test?

philipnorton42 commented 10 years ago

This is resolved.

Original Comment By: Philip Norton

philipnorton42 commented 10 years ago

If the test passes then no :)

Original Comment By: Philip Norton

philipnorton42 commented 10 years ago

Just ran the playbook with the test tag as you asked and it didn't throw the error (rolls eyes)...

Do you still want the output? :)

Original Comment By: Dan Bohea

philipnorton42 commented 10 years ago

Sorry - didn't get a chance today. Will email you as soon as I do.

Original Comment By: Dan Bohea

philipnorton42 commented 10 years ago

I've been trying to bran this all evening, but to no avail...

Would you be able to show me the output of the following:

ansible-playbook -i vlad/host.ini -t test vlad/playbooks/site.yml -vvvv

Email is fine, no need to put all of that output here! :)

Original Comment By: Philip Norton

philipnorton42 commented 10 years ago

It's worth adding that the most recent time it happened, the site's db hadn't yet been imported and so navigating to the site's URL would just show an SQL error.

Original Comment By: Dan Bohea

philipnorton42 commented 10 years ago

I'll take another look at it. I thought it might be due to an issue with already existing stuff in the docroot folder, but maybe that's not it...

Original Comment By: Philip Norton