Bug #11123

Archivematica vagrant box is broken

Added by Mike Gale over 2 years ago. Updated over 2 years ago.

Status:VerifiedStart date:04/27/2017
Priority:HighDue date:
Assignee:Hector Akamine% Done:

0%

Category:Development Environment
Target version:-
Google Code Legacy ID: Pull Request:
Sponsored:No Requires documentation:

Description

To reproduce:

Follow the arhcivematica.org instructions on either Ubuntu 14.04 or 16.04 that hasn't had an AM install before.

Expected result: the dev vagrant box should work

Error:

TASK [elasticsearch : Configuring Elasticsearch Node] ******************
fatal: [am-local]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to find 'elasticsearch.yml.j2' in expected paths."}
to retry, use: --limit @/home/moonshine/workspace/deploy-pub/playbooks/archivematica/singlenode.retry

PLAY RECAP *************************************************************
am-local : ok=25 changed=5 unreachable=0 failed=1

History

#1 Updated by Mike Gale over 2 years ago

Note I tried this on 2 different systems--Xubuntu 14.04 and vanilla Ubuntu 16.04 and got the same error, so I don't believe it's just me.

#2 Updated by Nick Wilkinson over 2 years ago

  • Assignee changed from Nick Wilkinson to Santiago Collazo

Hi Santi, assigning this to you to look into. https://trello.com/c/SY6S73M4

#3 Updated by Jesús García Crespo over 2 years ago

  • Status changed from New to Feedback
  • Assignee changed from Santiago Collazo to Mike Gale

Hi Mike, can you please let us know which version of Ansible are you using? Would you mind trying again with the latest version available?

#4 Updated by Mike Gale over 2 years ago

  • Assignee changed from Mike Gale to Santiago Collazo

using 2.3.0.0 ansible originally on ubuntu 16.04.

Tried to install from the official PPA, same issue (it also appears to be 2.3.0.0):

TASK [elasticsearch : Configuring Elasticsearch Node] ******************
fatal: [am-local]: FAILED! => {"changed": false, "failed": true, "msg": "Unable to find 'elasticsearch.yml.j2' in expected paths."}
to retry, use: --limit @/home/moonshine/workspace/deploy-pub/playbooks/archivematica/singlenode.retry

PLAY RECAP *************************************************************
am-local : ok=25 changed=5 unreachable=0 failed=1

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

#5 Updated by Mike Gale over 2 years ago

OK sorry some more information:

Jesús was able to reproduce my issue after upgrading ansible from 2.2.2.0 -> 2.3.0.0. It appears this is a known issue with generating the templates directory: https://github.com/ansible/ansible/issues/23597

This makes me think this might be a vendor issue and we can't do much about it, perhaps we should just put a note in our instructions temporarily to say which version we've tested + works in the AM docs? Maybe you can ask Justin what he wants to do Santi.

thanks!

#6 Updated by Santiago Collazo over 2 years ago

  • Assignee changed from Santiago Collazo to Mike Gale

Also, the problem only happens in os x , so I can't reproduce it. Did you try with ansible 2.4?

#7 Updated by Hector Akamine over 2 years ago

  • Status changed from Feedback to QA/Review

Was able to reproduce, proposed workaround to this ansible galaxy bug applied to the deploy-pub archivematica playbook in https://github.com/artefactual/deploy-pub/pull/32

#8 Updated by Mike Gale over 2 years ago

  • Status changed from QA/Review to Verified
  • Assignee changed from Mike Gale to Hector Akamine

Hi Hector,

I tested the new vagrant box and it appears to be working well. Thanks for fixing it, I'll mark this verified.

Also available in: Atom PDF