Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ansible instructions fails with "No hosts matched" #2

Open
rafabene opened this issue Apr 11, 2016 · 6 comments
Open

ansible instructions fails with "No hosts matched" #2

rafabene opened this issue Apr 11, 2016 · 6 comments

Comments

@rafabene
Copy link

To workaround the problem I commented out and run become: yes and become_method: sudo from setup.yml.

After that I ran ansible-playbook -i setup-host setup.yml -sk instead of ansible-playbook -i setup-host setup.yml -k

@rhuss
Copy link
Collaborator

rhuss commented Apr 11, 2016

Thanks for spotting this, wonder whether it works here. What Ansible version do you use ?

To be honest, I didn't thoroughly test the bootstrap process which is a bit rough.

@rhuss
Copy link
Collaborator

rhuss commented Apr 11, 2016

The version I use on OS X is:

nsible --version
ansible 2.0.0.2
  config file =
  configured module search path = Default w/o overrides

@rafabene
Copy link
Author

Ah! That explains much. I ran ansible from inside the pi. The version is: ansible 1.7.2. Shouldn't we add to the instructions that ansible2+ should be used and run from outside the pi ?

@rhuss
Copy link
Collaborator

rhuss commented Apr 11, 2016

Ouch, sorry that should be in the README for sure.

The general idea is to use Ansible only for provisioning the Pis and then is not needed anymore, so there is not much benefit to have Ansible on the Pis (the communication ansible -> pi goes all via SSH).

Thanks for spotting this ;)

BTW, wrt the roadmap:

  • I'm currently preparing a talk "Kubernetes for Java Developers" for next week at JAX2016 using the cluster as demo platform. For this I will tune the Kubernetes part (i.e. enable SkyDNS and add a registry).
  • A Blog post and enhanced documentation about the initial setup.
  • Afterwards I'll tackle OpenShift with an extra playbook. The idea is that you can easily switch between OpenShift and Kubernetes by running the appropriate playbook.

Any feedback is highly appreciated, let me know when I can help. I'm on irc, too (as @ro14nd on #fabric8 in Freenode)

rhuss added a commit that referenced this issue Apr 11, 2016
@Hades32
Copy link

Hades32 commented May 8, 2016

Concerning the become: yes etc., it would be good if this would be in a separate config file. Currently I have to change it in 4 different files as in my setup I can (only) connect directly as root.

@rhuss
Copy link
Collaborator

rhuss commented May 9, 2016

I will try to move the authentication configuration externally, good idea.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants