claw-playbook - blazegraph role fails at - Wait for blazegraph to expand

[Natkeeran]

Steps to reproduce

• cloned the latest vagrant 'commit cab799c67d92563205403eea89074cfbfc8b740e'
• vagrant up

Expected result

Ansible should provision the claw vagrant.

Actual result

Ansible fails with the following message:

TASK [blazegraph : Wait for blazegraph to expand] ******************************
fatal: [default]: FAILED! => {"changed": false, "elapsed": 300, "failed": true, "msg": "Timeout when waiting for file /var/lib/tomcat8/webapps/bigdata/WEB-INF/classes/log4j.properties"}
	to retry, use: --limit @/home/nat/Desktop/claw-playbook/playbook.retry

biddata.war seems to have been downloaded.

-rw-r--r-- 1 tomcat8 tomcat8 17465094 Sep  1 19:15 bigdata.war

Notes

Not sure if get_url would unpact the war. Times out waiting to find log4j.properties!
https://github.com/Islandora-Devops/claw-playbook/blob/0c43866b45b9670fda9ed858e728c87b78e8ad2b/roles/internal/blazegraph/tasks/download.yml#L4

[whikloj]

Just pulled the exact commit and started a vagrant up. I am not getting this error, could be a time out.

TASK [blazegraph : Create blazegraph home directory] ***************************
changed: [default]

TASK [blazegraph : Create blazegraph conf directory] ***************************
changed: [default]

TASK [blazegraph : Create blazegraph data directory] ***************************
changed: [default]

TASK [blazegraph : Copy templated blazegraph config files] *********************
changed: [default] => (item=RWStore.properties)

TASK [blazegraph : Copy blazegraph config files] *******************************
changed: [default] => (item=blazegraph.properties)
changed: [default] => (item=inference.nt)

TASK [blazegraph : Download blazegraph war] ************************************
changed: [default]

TASK [blazegraph : Wait for blazegraph to expand] ******************************
ok: [default]

TASK [blazegraph : Copy the templated log4j config] ****************************
changed: [default]

TASK [blazegraph : Setup namespace in blazegraph] ******************************
changed: [default]

TASK [blazegraph : Setup inference in blazegraph] ******************************
changed: [default]

[bryjbrown]

I'm using the same commit and it consistently errors out here:

TASK [webserver-app : Trusted Host Settings] ***********************************
fatal: [default]: FAILED! => {"changed": false, "failed": true, "msg": "unsupported parameter for module: path"}

RUNNING HANDLER [apache : restart apache] **************************************

RUNNING HANDLER [php : restart webserver] **************************************

RUNNING HANDLER [drupal : clear opcache] ***************************************
	to retry, use: --limit @/home/bryjbrown/Machines/claw-playbook/playbook.retry

PLAY RECAP *********************************************************************
default                    : ok=135  changed=49   unreachable=0    failed=1   

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

[whikloj]

@bryjbrown and your directory is clean correct? if you do git status there are no edited files? Normally I see that error when there is an indentation problem (joys of Yaml).

[jonathangreen]

What version of Ansible is everyone running?

[whikloj]

> ansible --version
ansible 2.3.2.0
  config file = /sw/var/www/DAM2/claw-playbook/ansible.cfg
  configured module search path = Default w/o overrides
  python version = 2.7.13 (default, Jul 18 2017, 09:16:53) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1)]

[bryjbrown]

claw-playbook % git status
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working tree clean
claw-playbook % ansible --version
ansible 2.2.1.0
  config file = /home/bryjbrown/Machines/claw-playbook/ansible.cfg
  configured module search path = Default w/o overrides

[jonathangreen]

http://docs.ansible.com/ansible/latest/blockinfile_module.html

The path argument was added in Ansible 2.3. I tend to think we should use the latest stable Ansible version, but I'm up for suggestions otherwise. Should probably go into the readme.

[bryjbrown]

@jonathangreen Agreed, I just started with whatever apt-get install ansible gave me. Just jumped through all the relevant hoops to get 2.3 on my system, vagrant uping now.

UPDATE: Upgrading to Ansible 2.3 did the trick for me, VM finished provisioning and is available.

[dannylamb]

@Natkeeran What version of Ansible are you running? We may be able to close this one out with documentation.

[Natkeeran]

@dannylamb

Was getting the same error for sometime, but after some time, I re-provisioned it and was not getting the same error.

nat@natubuntu:~/Desktop/claw-playbook$ ansible --version
ansible 2.3.2.0