mhamrah / ansible-mesos-playbook Goto Github PK

run into this problem on digitalocean

stderr: groupadd: group 'docker' already exists

Also, I needed to rename the "librarian-roles" directory to "roles" in order to make ansible run. Thanks for building this btw!

@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   

Stupid newbie questions: When using this via vagrant, with vagrant up ... how do I go about getting started? Can I access some kind of web ui via some port, or do I need to call things from inside the box only?

Offical way to install requirements is to use requirements.txt. See documentation here: http://docs.ansible.com/ansible/galaxy.html#advanced-control-over-role-requirements-files this would be beneficiial over using librarian by not requiring an extra dependency.

Confirm that the problem is Ubuntu

I got the msg "Could not fetch updated apt files", added 'cache_valid_time=3000' before

Line 7 in common.yml

I'm using ansible v1.9.2 on Ubuntu Server 14.04 to manage hosts running Ubuntu Server 14.04.

I could clone the repo and submit a pull, but this is a small (mostly documentation?) item, at least in my environment (ubuntu 14.04 against ec2 instances from any user account that is not named ubuntu on the machine executing ansible-playbook) executing ansible-playbook requires the "-u ubuntu" flag.

Hi,

I installed ansible and librarian-ansible. I'm trying to run 'librarian-ansible install' but it keeps failing with the following error. Am i missing something here? the syntax of the Ansiblefile should be correct (i'm using the one from this playbook). Any help would be appreciated!

[root@svdpdac015 ansible-mesos-playbook]# librarian-ansible install
/root/ansible-mesos-playbook/Ansiblefile:7:in run': compile error (SyntaxError) /root/ansible-mesos-playbook/Ansiblefile:7: syntax error, unexpected ':', expecting $end github: "mhamrah/ansible-docker" ^ from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/dsl.rb:79:inrun'
from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/dsl.rb:73:in tap' from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/dsl.rb:73:inrun'
from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/dsl.rb:17:in run' from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/environment.rb:148:indsl'
from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/specfile.rb:15:in read' from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/action/resolve.rb:17:inrun'
from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/cli.rb:169:in resolve!' from /usr/lib64/ruby/gems/1.8/gems/librarian-ansible-1.0.6/lib/librarian/ansible/cli.rb:41:ininstall'
from /usr/lib64/ruby/gems/1.8/gems/thor-0.19.1/lib/thor/command.rb:27:in __send__' from /usr/lib64/ruby/gems/1.8/gems/thor-0.19.1/lib/thor/command.rb:27:inrun'
from /usr/lib64/ruby/gems/1.8/gems/thor-0.19.1/lib/thor/invocation.rb:126:in invoke_command' from /usr/lib64/ruby/gems/1.8/gems/thor-0.19.1/lib/thor.rb:359:indispatch'
from /usr/lib64/ruby/gems/1.8/gems/thor-0.19.1/lib/thor/base.rb:440:in start' from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/cli.rb:26:inbin!'
from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/cli.rb:31:in returning_status' from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/cli.rb:26:inbin!'
from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/cli.rb:47:in with_environment' from /usr/lib64/ruby/gems/1.8/gems/librarian-0.1.2/lib/librarian/cli.rb:26:inbin!'
from /usr/lib64/ruby/gems/1.8/gems/librarian-ansible-1.0.6/bin/librarian-ansible:7
from /usr/bin/librarian-ansible:23:in `load'
from /usr/bin/librarian-ansible:23
[root@svdpdac015 ansible-mesos-playbook]#

Sonali

sym linking it fixed the issue, but using the instructions out of the readme result in the following error.

Workaround that seems to work: ln -s ./librarian_roles roles

Maybe a better solution is directing librarian to put stuff in roles (I don't know, I'm an ansible newbie)

ERROR: cannot find role in /home/vagrant/ansible-mesos-playbook/roles/ansible-docker or /home/vagrant/ansible-mesos-playbook/ansible-docker or /etc/ansible/roles/ansible-docker

Hi, this is very useful but getting to be over a year outdated. It would be nice if you updated the versions of mesos, marathon, docker, etc.