AnsibleUndefinedVariable: One or more undefined variables: list object has no element 2', 'failed':

[bigheadwen]

When I run make apply for a while ,it jump the error msg as follows:
TASK: [consul_base_agent | copy base.json] ************************************
fatal: [cdh-master-0.node.tapdeployment.consul] => {'msg': 'AnsibleUndefinedVariable: One or more undefined variables: list object has no element 2', 'failed': True}
fatal: [cdh-master-0.node.tapdeployment.consul] => {'msg': 'AnsibleUndefinedVariable: One or more undefined variables: list object has no element 2', 'failed': True}

FATAL: all hosts have already failed -- aborting
PLAY RECAP ********************************************************************
to retry, use: --limit @/home/centos/site.retry

cdh-manager.node.tapdeployment.consul : ok=13 changed=4 unreachable=0 failed=0
cdh-master-0.node.tapdeployment.consul : ok=22 changed=8 unreachable=1 failed=0
cdh-master-1.node.tapdeployment.consul : ok=17 changed=3 unreachable=0 failed=1
cdh-worker-0.node.tapdeployment.consul : ok=13 changed=3 unreachable=0 failed=0
cdh-worker-1.node.tapdeployment.consul : ok=13 changed=3 unreachable=0 failed=0

anyone who know how to fix it?Thanks!

[wkielas]

With the release of TAP 0.7 there were a lot of backwards incompatible changes in the automation - it looks like you've run into one of them (related to removing a separate CDH manager node).

There are two ways to fix this:

1. Use the platform-ansible scripts from the TAP-2016-APR-1 release. This requires ssh-ing into the cdh jump node and checking out the TAP-2016-APR-1 tag.
2. Use the deployment instructions for the 0.7 version (available here). You won't encounter the problem with the 0.7 infrastructure automation.

I highly recommend going with option number 2, since the new procedure is much easier to deploy and support.