Source
cars10k•

Not working as flawless as the first one for me. Ansible for example can't install applications because of missing rights. (adding "sudo: yes" worked it out)

Also i am missing apt-get update & upgrade in ansible

2
mehphpOP•

Ok, I have updated the tutorial to include updating/upgrading apt-get.

Where did you need to add sudo: yes? To each task.yml or in the playbook.yml?

Also, what OS are you using?

1
cars10k•

Guess i could have added it directly in the playbook for global use but i just added it to my nginx/main.yml . Otherwise it would throw errors like you get if you try to apt-get without sudo. I use the same os as you in the tutorial.

2
mehphpOP•

Hmm, I'm curious as to why the ansible.sudo = true in the Vagrantfile isn't working for you there.

If you clone and run the github repo, does that still give you the same error?

1
cars10k•

Well. My fault - guess i overlooked that one. Sorry! And thanks for your support.

2
LysanderArg•

Thanks for this! I think you should be advertising it in some way (I haven't seen it on r/webdev). More viewers = more feedback = better tutorials

2
mehphpOP•

Thanks for the kind words! I've already posted to r/webdev and will post each time I release a new tutorial (unless I receive negative feedback on that of course).

2
LysanderArg•

Talking about feedback, I found your post.

Something I found out about the people at /webdev is that they prefer direct links to the information. Look at your post for example - 6 votes, 73% positive, in 4 days. People got into it, curious about the part 2 of some tutorial (I'm talking about new people who aren't active suscribers), but didn't find a link to it, just a link to a sub-reddit. Bam! No upvote, no comments, no exposure.

I'm sorry, maybe I'm just being annoying right now, trying to tell you how to do this stuff, but I'd really like more people to find out about this series of tutorials. I just don't want to see you one day thinking 'Huh... People aren't commenting as much as they used to... Maybe no one is interested on these after all', and we end up with no more articles.

1
mehphpOP•

Oh no worries at all, I appreciate the tips for sure. I don't want to feel like I'm spamming webdev but I'll definitely directly link to the next one.

Btw will finish this series regardless of the feedback. I'm thinking there will be two more, one for task runners and the last one will be using the same ansible scripts to provision a digital ocean server.

I'm open to suggestions if anything is missing or if there is another area of workflow people want covered.

2
rastur42•

Heya. I am trying to run this on a windows host. Got the latest vagrant with ansible_local.

When i run the provision i get:

 

There are errors in the configuration of this machine. Please fix
the following errors and try again:

ansible local provisioner:
* `playbook` does not exist on the guest: D:/provisioning/playbook.yml

 

I have tried to play around with the playbook path, but could not get rid of that D:/. What am i missing?

 

EDIT: Found a solution.

https://github.com/mitchellh/vagrant/commit/07f3d0b00dabc37281a01c6776eed22daeea7066

 

So now the provisioner runs but it stops with the following:

 

==> default: Running provisioner: ansible_local...
    default: Installing Ansible...
The Ansible software could not be found! Please verify
that Ansible is correctly installed on your guest system.

 

Am i supposed to install ansible on the guest machine and then rerun the provisioner? This kinda sucks.

1
mehphpOP•

Am i supposed to install ansible on the guest machine and then rerun the provisioner? This kinda sucks.

Agreed, but I don't think you have to do quite that. According to the docs:

Starting in version 1.7, Ansible also contains support for managing Windows machines. This uses native PowerShell remoting, rather than SSH. Ansible will still be run from a Linux control machine, and uses the “winrm” Python module to talk to remote hosts. No additional software needs to be installed on the remote machines for Ansible to manage them, it still maintains the agentless properties that make it popular on Linux/Unix.

So it appears that you shouldn't have to install anything on the guest machine as far as I can tell; instead you you still run in through another linux control machine. I don't have access to a windows machine otherwise I'd try it for myself.

I was unaware of the major differences in how Ansible works with Windows before starting this tutorial

1
rastur42•

Yes, the whole windows thing is a headache, agree. It would seem there is some merit to what you said. After looking through vagrant files it would appear that when using ansible_local the provisioner would attempt to install ansible on target machine and run the provision. But alas, it fails.

 

So i have tried to install it manually, thinking of something like hey, i can install ansible via shell script first and then run provision. Well, no cigar. Provisioner claims there is no ansible present. Maybe this could work, but i haven't got the foggiest idea how to setup ansible ssh keys on vagrant and host machine.

 

So as a next step i have tried to get ansible to run on windows and use ansible and not ansible_local. Long story short: just don't. Pity tho. Ansible looks really nice and simple. I had this wish to set up a simple, custom tailored dev machine for my needs. I guess i will stick with Puphpet with all its bloated and convoluted glory. Also, i need a mac :/

 

Well one final solution would be run to do a little ansileinception and spin up a vm with ansible to provision another target one. But that kinda defies the purpose, would't you agree? In any case, thanks man. It's been fun and you have taught me allot!

1
mehphpOP•

No problem and sorry it's such a pain on windows.

The next part in the serious will be on task-runners though which does work on windows.

1
wishicouldcode•

I am not sure if I missed something, but my ~/Projects/tutorial1/.vagrant/ folder does not have a provisioners folder..

EDIT: never mind, I had to run vagrant provision after creating the playbook.yml. Doh.

1
mehphpOP•

what happens when you run vagrant up --provision in the ~/Projects/tutorial1/ directory?

1
wishicouldcode•

Sorry, yes I realized that minutes after posting that comment that I need to run provision (the tutorial does not explicitly state this). I did not delete my comment in case anyone else encountered this.

1
[deleted]•

[removed]

1