Ansible 2.4.2.0 on CentOS 7--ping module isn't working

Obsolesce

You should give SaltStack a go as well. I think it's quite a bit easier to use.

matteo nunziati

@wirestyle22 said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@black3dynamite That looks so weird to me

shouldn't the host be ansible_host=hostname ? Did they change that?

Please post your inventory well formatted as code. It should contain a list of targets and should be passed to ansible with the -i flag. Also check the docs: https://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html

stacksofplates

Dont' pass ansible_host= in the command line. That's defined in your inventory file. You also don't need to add that in your inventory file at all since you've defined it in your /etc/hosts file. I never add the password in the inventory. If I don't have a key on the other end I just pass -k in the command. So you would do this:

ansible -i inventory ansible-target1 -m ping -k

Also make sure every host is on a separate line in your inventory. I noticed you only did > instead of >>. You could have only put one host in, but figured I'd mention it just in case.

stacksofplates

Also 2.4.2 is kind of old. Some things are being deprecated soon, so you will want to either install from EPEL or use pip to pull in a newer version.

scottalanmiller

@stacksofplates said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

Also 2.4.2 is kind of old. Some things are being deprecated soon, so you will want to either install from EPEL or use pip to pull in a newer version.

Another "CentOS problem" that "doesn't exist"

stacksofplates

@scottalanmiller said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@stacksofplates said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

Also 2.4.2 is kind of old. Some things are being deprecated soon, so you will want to either install from EPEL or use pip to pull in a newer version.

Another "CentOS problem" that "doesn't exist"

Well it's weird. Idk if CentOS hasn't caught up with RHEL yet or what's going on. Ansible is at 2.7 in RHEL. I have no idea why it's lagging so far behind in CentOS.

scottalanmiller

@stacksofplates said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@scottalanmiller said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@stacksofplates said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

Also 2.4.2 is kind of old. Some things are being deprecated soon, so you will want to either install from EPEL or use pip to pull in a newer version.

Another "CentOS problem" that "doesn't exist"

Well it's weird. Idk if CentOS hasn't caught up with RHEL yet. Ansible is at 2.7 in RHEL. I have no idea why it's lagging so far behind in CentOS.

oh, weird.

stacksofplates

@scottalanmiller said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@stacksofplates said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@scottalanmiller said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@stacksofplates said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

Also 2.4.2 is kind of old. Some things are being deprecated soon, so you will want to either install from EPEL or use pip to pull in a newer version.

Another "CentOS problem" that "doesn't exist"

Well it's weird. Idk if CentOS hasn't caught up with RHEL yet. Ansible is at 2.7 in RHEL. I have no idea why it's lagging so far behind in CentOS.

oh, weird.

But even Fedora lags behind a little. It's getting better but I've seen it as far as 2 releases behind before.

wirestyle22

@matteo-nunziati said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@wirestyle22 said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@black3dynamite That looks so weird to me

shouldn't the host be ansible_host=hostname ? Did they change that?

Please post your inventory well formatted as code. It should contain a list of targets and should be passed to ansible with the -i flag. Also check the docs: https://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html

This is a basic ping check with a basic inventory file. Originally it was this but I have removed the ssh password portion.

ansible-target1 ansible_host=192.168.1.208 ansible_ssh_pass=password
ansible-target2 ansible_host=192.168.1.209 ansible_ssh_pass=password

wirestyle22

@stacksofplates said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

Dont' pass ansible_host= in the command line. That's defined in your inventory file. You also don't need to add that in your inventory file at all since you've defined it in your /etc/hosts file. I never add the password in the inventory. If I don't have a key on the other end I just pass -k in the command. So you would do this:
ansible -i inventory ansible-target1 -m ping -k
Also make sure every host is on a separate line in your inventory. I noticed you only did > instead of >>. You could have only put one host in, but figured I'd mention it just in case.

God you're handsome.

Time to screw around with YAML.

Obsolesce

Or in Salt:

salt pcname test.ping

stacksofplates

@Obsolesce said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

Or in Salt:

salt pcname test.ping

It's much simpler if you have your ansible.cfg and keys set up. Then it's just ansible server -m ping.

This is like trying to use Salt without having certs set up (or SSH keys in the case of salt-ssh)

Obsolesce

@stacksofplates said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@Obsolesce said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

Or in Salt:

salt pcname test.ping

It's much simpler if you have your ansible.cfg and keys set up. Then it's just ansible server -m ping.

This is like trying to use Salt without having certs set up (or SSH keys in the case of salt-ssh)

If you want to use ssh as a transport, but not needed or why you'd choose Salt. If that's the case then I'd rather want to use Ansible.

stacksofplates

@Obsolesce said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@stacksofplates said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@Obsolesce said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

Or in Salt:

salt pcname test.ping

It's much simpler if you have your ansible.cfg and keys set up. Then it's just ansible server -m ping.

This is like trying to use Salt without having certs set up (or SSH keys in the case of salt-ssh)

If you want to use ssh as a transport, but not needed or why you'd choose Salt. If that's the case then I'd rather want to use Ansible.

I want saying you should. Just once things are set up properly they are both (Ansible and Salt) very similar in ease of use.

matteo nunziati

@stacksofplates said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@scottalanmiller said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@stacksofplates said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@scottalanmiller said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@stacksofplates said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

Also 2.4.2 is kind of old. Some things are being deprecated soon, so you will want to either install from EPEL or use pip to pull in a newer version.

Another "CentOS problem" that "doesn't exist"

Well it's weird. Idk if CentOS hasn't caught up with RHEL yet. Ansible is at 2.7 in RHEL. I have no idea why it's lagging so far behind in CentOS.

oh, weird.

But even Fedora lags behind a little. It's getting better but I've seen it as far as 2 releases behind before.

I always download it from upstream

wirestyle22

@stacksofplates How are you organizing? I have playbooks and inventory together in the same directory right now. Seems bad. Also, are you using an IDE?

wirestyle22

Another way to do this ping test:

pingtest.yml

-
  name: Test connectivity to target servers
  hosts: all
  tasks:
   - name: Ping test
     ping:

black3dynamite

@wirestyle22 said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@stacksofplates How are you organizing? I have playbooks and inventory together in the same directory right now. Seems bad. Also, are you using an IDE?

Here are some best practices for directory layouts.

https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html#directory-layout

https://docs.ansible.com/ansible/latest/user_guide/playbooks_best_practices.html#alternative-directory-layout

stacksofplates

@wirestyle22 said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@stacksofplates How are you organizing? I have playbooks and inventory together in the same directory right now. Seems bad. Also, are you using an IDE?

I'll give you a layout this afternoon. I keep my inventory with my playbooks but roles have their own repositories.

stacksofplates

@wirestyle22 said in Ansible 2.4.2.0 on CentOS 7--ping module isn't working:

@stacksofplates How are you organizing? I have playbooks and inventory together in the same directory right now. Seems bad. Also, are you using an IDE?

So I have my playbooks set up like this (for stuff at home). I've seen people put playbooks in a directory which is fine as well. It's just annoying because your ansible.cfg has to be in relation to your playbooks so you had to mess around with softlinks to get it to work that way.

Roles (ones I've written) are in their own directory:

Here's my default ansible.cfg which I store with the playbooks:

[defaults]
inventory           = inventory
roles_path          = roles
retry_files_enabled = False
pipelining          = True
library             = library
forks               = 50
callback_whitelist = profile_roles

And then in the inventory directory I have a prod and dev file that contain all of the groups and hosts.

Also, are you using an IDE?

I switch between VS Code and Vim. However I always turn on Vim mode in anything. I also have things like jj mapped to Esc and AA mapped to drop me to the end of a line in insert mode to make things easier.