New run of Ansible playbooks locally to create development environment fails at "Turn off shard allocation" task

Description

Discovered while rebuilding my local dev environment to try addressing #7714.

<pre>
PLAY [Gather inventory facts in case playbook is run standalone] **************

GATHERING FACTS ***************************************************************
ok: [loadbal]
ok: [dbnode2]
ok: [webapp1]
ok: [dbnode1]

PLAY [127.0.0.1] **************************************************************

GATHERING FACTS ***************************************************************
ok: [127.0.0.1]

TASK: [Turn off shard replica allocation] *************************************
failed: [127.0.0.1 -> 127.0.0.1] => {"changed": true, "rc": 1}
stderr: Elasticsearch request failed:
<html><body><h1>503 Service Unavailable</h1> No server is available to handle this request. </body></html>

FATAL: all hosts have already failed – aborting
</pre>

Activity

Show:
Mark Breedlove
October 18, 2014, 6:20 AM

Sorry about that. I'd simply forgotten to update the README. There's a parameter you have to pass to `ansible-playbook` for an initial configuration run: `--extra-vars "initial_run=true"`

I've updated the README:
https://github.com/dpla/automation/commit/d04827eeb64a963a25d2aa9166461fafdaaadea9

Mark Matienzo
October 20, 2014, 12:38 PM

Got it - thanks!

Done

Assignee

Mark Breedlove

Reporter

Mark Matienzo

Labels

None

Priority

Low