mhamrah / ansible-mesos-playbook

An ansible playbook for launching a mesos cluster with docker and marathon support.
MIT License
151 stars 60 forks source link

fatal: [master1] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True} #5

Closed adilnaimi closed 10 years ago

adilnaimi commented 10 years ago

@mhamrah thank you very much for the great job. While trying to build the cluster, the following TASK fails:

[./librarian_roles/ansible-mesos | Create zookeeper config file] ******** 
TASK: [./librarian_roles/ansible-mesos | Create zookeeper config file] ******** 
fatal: [master1] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True}
fatal: [master1] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True}
fatal: [master2] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True}
fatal: [master2] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True}
fatal: [master3] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True}
fatal: [master3] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True}

FATAL: all hosts have already failed -- aborting

PLAY RECAP ******************************************************************** 
           to retry, use: --limit @/home/me/playbook.retry

master1               : ok=15   changed=6    unreachable=1    failed=0   
master2               : ok=15   changed=6    unreachable=1    failed=0   
master3               : ok=15   changed=6    unreachable=1    failed=0   
mhamrah commented 10 years ago

I think you're missing the zoo_id variable when declaring masters in your hosts file. Check out the sample and make sure each master has a zoo_id specified.

On Thu, Oct 9, 2014 at 7:36 PM, Adil NAIMI notifications@github.com wrote:

@mhamrah https://github.com/mhamrah thank you very much for the great job. While trying to build the cluster, the following TASK fails:

[./librarian_roles/ansible-mesos | Create zookeeper config file] ****

TASK: [./librarian_roles/ansible-mesos | Create zookeeper config file] **** fatal: [master1] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True} fatal: [master1] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True} fatal: [master2] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True} fatal: [master2] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True} fatal: [master3] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True} fatal: [master3] => {'msg': "AnsibleUndefinedVariable: One or more undefined variables: 'dict object' has no attribute 'zoo_id'", 'failed': True}

FATAL: all hosts have already failed -- aborting

PLAY RECAP **** to retry, use: --limit @/home/me/playbook.retry

master1 : ok=15 changed=6 unreachable=1 failed=0 master2 : ok=15 changed=6 unreachable=1 failed=0 master3 : ok=15 changed=6 unreachable=1 failed=0

— Reply to this email directly or view it on GitHub https://github.com/mhamrah/ansible-mesos-playbook/issues/5.

adilnaimi commented 9 years ago

Yes exactly. After adding the zoo_id, build done succefely

triplepoint commented 8 years ago

It's worth asking why those errors were marked as "unreachable". We've just run into a similar issue ourselves with ansible 1.7.2. I would expect "failed" for these AnsibleUnidentifiedVariable errors.