Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Hello Andrey,

I try to update ansible.cfg with below content. But still getting same error. Can you please check whether added variable is correct or not? Anything else we need to do.

This is my ansible.cfg file, in lieu of discovered_interpreter_python I used ansible_python_interpreter but same issue. I also try to use this ansible_python_interpreter: /opt/freeware/bin/python3 

 cat ansible.cfg
[defaults]
inventory=/home/automation/ansible/systemfiles/inventory
log_path=/home/automation/ansible/systemfiles/ansible_logs
discovered_interpreter_python=/opt/freeware/bin/python3
forks=10
interpreter_python=auto_silent

[privilege_escalation]
become=true
become_user=root
become_method=sudo

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Hello Andrey,

I try to update ansible.cfg with below content. But still getting same error. Can you please check whether added variable is correct or not? Anything else we need to do.

This is my ansible.cfg file, in lieu of discovered_interpreter_python I used ansible_python_interpreter but same issue. I also try to use this ansible_python_interpreter: /opt/freeware/bin/python3 

 cat ansible.cfg
[defaults]
inventory=/home/automation/ansible/systemfiles/inventory
log_path=/home/automation/ansible/systemfiles/ansible_logs
discovered_interpreter_python=/opt/freeware/bin/python3
forks=10
interpreter_python=auto_silent

[privilege_escalation]
become=true
become_user=root
become_method=sudo

Hello Andrey,

I try to update ansible.cfg with below content. But still getting same error. Can you please check whether added variable is correct or not? Anything else we need to do.

This is my ansible.cfg file, in lieu of discovered_interpreter_python I used ansible_python_interpreter but same issue. I also try to use this ansible_python_interpreter: /opt/freeware/bin/python3 

 cat ansible.cfg
[defaults]
inventory=/home/automation/ansible/systemfiles/inventory
log_path=/home/automation/ansible/systemfiles/ansible_logs
discovered_interpreter_python=/opt/freeware/bin/python3
forks=10
interpreter_python=auto_silent

[privilege_escalation]
become=true
become_user=root
become_method=sudo

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Hello Andrey,

I try to update ansible.cfg with below content. But still getting same error. Can you please check whether added variable is correct or not? Anything else we need to do.

This is my ansible.cfg file, in lieu of discovered_interpreter_python I used ansible_python_interpreter but same issue. I also try to use this ansible_python_interpreter: /opt/freeware/bin/python3 

 cat ansible.cfg
[defaults]
inventory=/home/automation/ansible/systemfiles/inventory
log_path=/home/automation/ansible/systemfiles/ansible_logs
discovered_interpreter_python=/opt/freeware/bin/python3
forks=10
interpreter_python=auto_silent

[privilege_escalation]
become=true
become_user=root
become_method=sudo

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Hello Manoj,

please try:

interpreter_python = /opt/freeware/bin/python3

instead of discovered_interpreter_python=/opt/freeware/bin/python3

Hello Andrey,

I try to update ansible.cfg with below content. But still getting same error. Can you please check whether added variable is correct or not? Anything else we need to do.

This is my ansible.cfg file, in lieu of discovered_interpreter_python I used ansible_python_interpreter but same issue. I also try to use this ansible_python_interpreter: /opt/freeware/bin/python3 

 cat ansible.cfg
[defaults]
inventory=/home/automation/ansible/systemfiles/inventory
log_path=/home/automation/ansible/systemfiles/ansible_logs
discovered_interpreter_python=/opt/freeware/bin/python3
forks=10
interpreter_python=auto_silent

[privilege_escalation]
become=true
become_user=root
become_method=sudo

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Thanks Andrey, it is working now. Really appreciate to working with all of you guys. 

Further addition to that, in this scenario we have Linux controller node and agent are AIX and Linux both. But we use AIX controller node how we can setup the same thing. We have installing ansible with python3 on one of AIX node. We used same dnf method to install all packages. Now when we are running ansbile -m ping all command, it is giving below error. 

root@server3:/# ansible -m ping all
Server1 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server1: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
server2 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server2: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
localhost | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
server3| SUCCESS => {
    "changed": false,
    "ping": "pong"
}

Hello Manoj,

please try:

interpreter_python = /opt/freeware/bin/python3

instead of discovered_interpreter_python=/opt/freeware/bin/python3

Hello Andrey,

I try to update ansible.cfg with below content. But still getting same error. Can you please check whether added variable is correct or not? Anything else we need to do.

This is my ansible.cfg file, in lieu of discovered_interpreter_python I used ansible_python_interpreter but same issue. I also try to use this ansible_python_interpreter: /opt/freeware/bin/python3 

 cat ansible.cfg
[defaults]
inventory=/home/automation/ansible/systemfiles/inventory
log_path=/home/automation/ansible/systemfiles/ansible_logs
discovered_interpreter_python=/opt/freeware/bin/python3
forks=10
interpreter_python=auto_silent

[privilege_escalation]
become=true
become_user=root
become_method=sudo

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Glad to hear that it works.

As @Stephen Ulmer wrote, if you have different classes of clients with different paths to python, it is better to define path to python in inventory or in playbooks. You have two different classes - Linux boxes and AIX boxes. Your inventory could look like:

linux1 ansible_python_interpreter=/usr/bin/python3linux2 ansible_python_interpreter=/usr/bin/python3aix1 ansible_python_interpreter=/opt/freeware/bin/python3aix2 ansible_python_interpreter=/opt/freeware/bin/python3

Your error "Failed to connect to the host via ssh: root@server2: Permission denied (publickey,password,keyboard-interactive)." usually means that you didn't exchange SSH keys between your Ansible controller node and the managed node (server2).

Try to execute on the Ansible controller node:

ssh-copy-id root@server2

It will copy your public key (if you have it) from the Ansible controller node to the managed node server2.

Thanks Andrey, it is working now. Really appreciate to working with all of you guys. 

Further addition to that, in this scenario we have Linux controller node and agent are AIX and Linux both. But we use AIX controller node how we can setup the same thing. We have installing ansible with python3 on one of AIX node. We used same dnf method to install all packages. Now when we are running ansbile -m ping all command, it is giving below error. 

root@server3:/# ansible -m ping all
Server1 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server1: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
server2 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server2: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
localhost | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
server3| SUCCESS => {
    "changed": false,
    "ping": "pong"
}

Hello Manoj,

please try:

interpreter_python = /opt/freeware/bin/python3

instead of discovered_interpreter_python=/opt/freeware/bin/python3

Hello Andrey,

I try to update ansible.cfg with below content. But still getting same error. Can you please check whether added variable is correct or not? Anything else we need to do.

This is my ansible.cfg file, in lieu of discovered_interpreter_python I used ansible_python_interpreter but same issue. I also try to use this ansible_python_interpreter: /opt/freeware/bin/python3 

 cat ansible.cfg
[defaults]
inventory=/home/automation/ansible/systemfiles/inventory
log_path=/home/automation/ansible/systemfiles/ansible_logs
discovered_interpreter_python=/opt/freeware/bin/python3
forks=10
interpreter_python=auto_silent

[privilege_escalation]
become=true
become_user=root
become_method=sudo

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Glad to hear that it works.

As @Stephen Ulmer wrote, if you have different classes of clients with different paths to python, it is better to define path to python in inventory or in playbooks. You have two different classes - Linux boxes and AIX boxes. Your inventory could look like:

linux1 ansible_python_interpreter=/usr/bin/python3
linux2 ansible_python_interpreter=/usr/bin/python3
aix1 ansible_python_interpreter=/opt/freeware/bin/python3
aix2 ansible_python_interpreter=/opt/freeware/bin/python3

Your error "Failed to connect to the host via ssh: root@server2: Permission denied (publickey,password,keyboard-interactive)." usually means that you didn't exchange SSH keys between your Ansible controller node and the managed node (server2).

Try to execute on the Ansible controller node:

ssh-copy-id root@server2

It will copy your public key (if you have it) from the Ansible controller node to the managed node server2.

Thanks Andrey, it is working now. Really appreciate to working with all of you guys. 

Further addition to that, in this scenario we have Linux controller node and agent are AIX and Linux both. But we use AIX controller node how we can setup the same thing. We have installing ansible with python3 on one of AIX node. We used same dnf method to install all packages. Now when we are running ansbile -m ping all command, it is giving below error. 

root@server3:/# ansible -m ping all
Server1 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server1: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
server2 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server2: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
localhost | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
server3| SUCCESS => {
    "changed": false,
    "ping": "pong"
}

Hello Manoj,

please try:

interpreter_python = /opt/freeware/bin/python3

instead of discovered_interpreter_python=/opt/freeware/bin/python3

Hello Andrey,

I try to update ansible.cfg with below content. But still getting same error. Can you please check whether added variable is correct or not? Anything else we need to do.

This is my ansible.cfg file, in lieu of discovered_interpreter_python I used ansible_python_interpreter but same issue. I also try to use this ansible_python_interpreter: /opt/freeware/bin/python3 

 cat ansible.cfg
[defaults]
inventory=/home/automation/ansible/systemfiles/inventory
log_path=/home/automation/ansible/systemfiles/ansible_logs
discovered_interpreter_python=/opt/freeware/bin/python3
forks=10
interpreter_python=auto_silent

[privilege_escalation]
become=true
become_user=root
become_method=sudo

Thanks Andrey, it is working now. Really appreciate to working with all of you guys. 

Further addition to that, in this scenario we have Linux controller node and agent are AIX and Linux both. But we use AIX controller node how we can setup the same thing. We have installing ansible with python3 on one of AIX node. We used same dnf method to install all packages. Now when we are running ansbile -m ping all command, it is giving below error. 

root@server3:/# ansible -m ping all
Server1 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server1: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
server2 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server2: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
localhost | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
server3| SUCCESS => {
    "changed": false,
    "ping": "pong"
}

Hello Manoj,

please try:

interpreter_python = /opt/freeware/bin/python3

instead of discovered_interpreter_python=/opt/freeware/bin/python3

Hello Andrey,

I try to update ansible.cfg with below content. But still getting same error. Can you please check whether added variable is correct or not? Anything else we need to do.

This is my ansible.cfg file, in lieu of discovered_interpreter_python I used ansible_python_interpreter but same issue. I also try to use this ansible_python_interpreter: /opt/freeware/bin/python3 

 cat ansible.cfg
[defaults]
inventory=/home/automation/ansible/systemfiles/inventory
log_path=/home/automation/ansible/systemfiles/ansible_logs
discovered_interpreter_python=/opt/freeware/bin/python3
forks=10
interpreter_python=auto_silent

[privilege_escalation]
become=true
become_user=root
become_method=sudo

Thanks Andrey, it is working now. Really appreciate to working with all of you guys. 

Further addition to that, in this scenario we have Linux controller node and agent are AIX and Linux both. But we use AIX controller node how we can setup the same thing. We have installing ansible with python3 on one of AIX node. We used same dnf method to install all packages. Now when we are running ansbile -m ping all command, it is giving below error. 

root@server3:/# ansible -m ping all
Server1 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server1: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
server2 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server2: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
localhost | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
server3| SUCCESS => {
    "changed": false,
    "ping": "pong"
}

Hello Manoj,

please try:

interpreter_python = /opt/freeware/bin/python3

instead of discovered_interpreter_python=/opt/freeware/bin/python3

Hello Andrey,

I try to update ansible.cfg with below content. But still getting same error. Can you please check whether added variable is correct or not? Anything else we need to do.

This is my ansible.cfg file, in lieu of discovered_interpreter_python I used ansible_python_interpreter but same issue. I also try to use this ansible_python_interpreter: /opt/freeware/bin/python3 

 cat ansible.cfg
[defaults]
inventory=/home/automation/ansible/systemfiles/inventory
log_path=/home/automation/ansible/systemfiles/ansible_logs
discovered_interpreter_python=/opt/freeware/bin/python3
forks=10
interpreter_python=auto_silent

[privilege_escalation]
become=true
become_user=root
become_method=sudo

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Hello Team,

One thing would like to know that once we run ./dnf_aixtoolbox.sh is gives below 3 option (flag) for installation. So which method would you prefer to use. We have to install across the AIX servers. 

and How we can remediate any future vulnerability or update related to ansible on AIX?

Thanks Andrey, it is working now. Really appreciate to working with all of you guys. 

Further addition to that, in this scenario we have Linux controller node and agent are AIX and Linux both. But we use AIX controller node how we can setup the same thing. We have installing ansible with python3 on one of AIX node. We used same dnf method to install all packages. Now when we are running ansbile -m ping all command, it is giving below error. 

root@server3:/# ansible -m ping all
Server1 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server1: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
server2 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server2: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
localhost | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
server3| SUCCESS => {
    "changed": false,
    "ping": "pong"
}

Hello Manoj,

please try:

interpreter_python = /opt/freeware/bin/python3

instead of discovered_interpreter_python=/opt/freeware/bin/python3

Hello Andrey,

I try to update ansible.cfg with below content. But still getting same error. Can you please check whether added variable is correct or not? Anything else we need to do.

This is my ansible.cfg file, in lieu of discovered_interpreter_python I used ansible_python_interpreter but same issue. I also try to use this ansible_python_interpreter: /opt/freeware/bin/python3 

 cat ansible.cfg
[defaults]
inventory=/home/automation/ansible/systemfiles/inventory
log_path=/home/automation/ansible/systemfiles/ansible_logs
discovered_interpreter_python=/opt/freeware/bin/python3
forks=10
interpreter_python=auto_silent

[privilege_escalation]
become=true
become_user=root
become_method=sudo

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Hi Manoj,

I personally almost always use -y. I like to have a compatibility layer to yum. In many different documentation or presentations you still can find references to yum and it is easier for me if I have yum command as an alias to dnf. The same does Red Hat Enterprise Linux, where you have both yum and dnf commands. 

Regarding updates of Ansible on AIX. I use Ansible from AIX Toolbox. It means if there is a new version of Ansible available, I can always update it using either:

dnf -y update

or Ansible itself:

- hosts: all  gather_facts: no  vars:    ansible_python_interpreter: /opt/freeware/bin/python3  tasks:  - name: update all packages    dnf:      name: '*'      state: latest

ansible-playbook -c local -i localhost, dnf-update.yml

I hope IBM will publish a new Ansible version if there are vulnerabilities in the existing one ;-)

Hello Team,

One thing would like to know that once we run ./dnf_aixtoolbox.sh is gives below 3 option (flag) for installation. So which method would you prefer to use. We have to install across the AIX servers. 

and How we can remediate any future vulnerability or update related to ansible on AIX?

Thanks Andrey, it is working now. Really appreciate to working with all of you guys. 

Further addition to that, in this scenario we have Linux controller node and agent are AIX and Linux both. But we use AIX controller node how we can setup the same thing. We have installing ansible with python3 on one of AIX node. We used same dnf method to install all packages. Now when we are running ansbile -m ping all command, it is giving below error. 

root@server3:/# ansible -m ping all
Server1 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server1: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
server2 | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: root@server2: Permission denied (publickey,password,keyboard-interactive).",
    "unreachable": true
}
localhost | SUCCESS => {
    "changed": false,
    "ping": "pong"
}
server3| SUCCESS => {
    "changed": false,
    "ping": "pong"
}

Hello Manoj,

please try:

interpreter_python = /opt/freeware/bin/python3

instead of discovered_interpreter_python=/opt/freeware/bin/python3

Hello Andrey,

I try to update ansible.cfg with below content. But still getting same error. Can you please check whether added variable is correct or not? Anything else we need to do.

This is my ansible.cfg file, in lieu of discovered_interpreter_python I used ansible_python_interpreter but same issue. I also try to use this ansible_python_interpreter: /opt/freeware/bin/python3 

 cat ansible.cfg
[defaults]
inventory=/home/automation/ansible/systemfiles/inventory
log_path=/home/automation/ansible/systemfiles/ansible_logs
discovered_interpreter_python=/opt/freeware/bin/python3
forks=10
interpreter_python=auto_silent

[privilege_escalation]
become=true
become_user=root
become_method=sudo

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

One thing would like to add the controlled node here is Linux. 

One thing would like to add the controlled node here is Linux. 

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

We installed python on few servers and it is working fine on few servers but today when we try to install it on 2 or more servers. It's not working.

Method which we used for installation on AIX.
First download the dnf script and copy it to client.
Then run ./dnf_aixtoolbox.sh -d from the client. 
After that command successfully executed, we have updated the packages to latest level with ./dnf update command.
copy controller node public key into client authorized keys. 

After that I tried to run ansible -m ping all but it gives below error. Could you please suggest what is next steps. 

Regards
Manoj

One thing would like to add the controlled node here is Linux. 

We installed python on few servers and it is working fine on few servers but today when we try to install it on 2 or more servers. It's not working.

Method which we used for installation on AIX.
First download the dnf script and copy it to client.
Then run ./dnf_aixtoolbox.sh -d from the client. 
After that command successfully executed, we have updated the packages to latest level with ./dnf update command.
copy controller node public key into client authorized keys. 

After that I tried to run ansible -m ping all but it gives below error. Could you please suggest what is next steps. 

Regards
Manoj

One thing would like to add the controlled node here is Linux. 

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Hi!

dsmjca71img | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: Shared connection to dsmjca71img closed.",
    "unreachable": true
}

First thing I would investigate is, if you actually connect to that host via ssh passwordless.


Best regards,
  Alexander

We installed python on few servers and it is working fine on few servers but today when we try to install it on 2 or more servers. It's not working.

Method which we used for installation on AIX.
First download the dnf script and copy it to client.
Then run ./dnf_aixtoolbox.sh -d from the client. 
After that command successfully executed, we have updated the packages to latest level with ./dnf update command.
copy controller node public key into client authorized keys. 

After that I tried to run ansible -m ping all but it gives below error. Could you please suggest what is next steps. 

Regards
Manoj

One thing would like to add the controlled node here is Linux. 

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html

Hi again!

From your reply I got, that you can ping as well as ssh works without problems.

Then I would suggest to check whether your configured python interpreter works, and then whether your become method "sudo" works.

So best try from your ansible host try to log in via ssh:
ssh dsmjca71img
Then try to start the python interpreter you configured. It should look similar to:
root@dsmjca71img:/root # /opt/freeware/bin/python3
Python 3.7.9 (default, Mar 30 2021, 00:48:16) 
[GCC 8.3.0] on aix7
Type "help", "copyright", "credits" or "license" for more information.
>>> 

And if that works, try to run sudo, as you configured that as your become method. For example by running sudo -l:
root@dsmjca71img:/root # sudo -l
User root may run the following commands on dsmjca71img:
    (ALL) NOPASSWD: ALL

Note:  I don't think you require a become method, if you connect as root anyway. But as you have it configured, I guess it might cause the above failure.


If ssh, python and sudo works, your ansible should work.  If it still doesn't work, I'm running out of ideas, what might be the problem.


Best regards,
  Alexander

Hi!

dsmjca71img | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: Shared connection to dsmjca71img closed.",
    "unreachable": true
}

First thing I would investigate is, if you actually connect to that host via ssh passwordless.


Best regards,
  Alexander

We installed python on few servers and it is working fine on few servers but today when we try to install it on 2 or more servers. It's not working.

Method which we used for installation on AIX.
First download the dnf script and copy it to client.
Then run ./dnf_aixtoolbox.sh -d from the client. 
After that command successfully executed, we have updated the packages to latest level with ./dnf update command.
copy controller node public key into client authorized keys. 

After that I tried to run ansible -m ping all but it gives below error. Could you please suggest what is next steps. 

Regards
Manoj

One thing would like to add the controlled node here is Linux. 

Hi Manoj,

Ansible looks for python interpreter in /usr/bin/python. Old RPM packages created a symlink in /usr/bin for python binaries. New RPM packages don't do it anymore. Because you didn't provide any error message, I can suppose that this is the reason for your failure - the failing server doesn't have /usr/bin/python.

The choices you have:

• create symlinks in /usr/bin. I wouldn't recommend unless you know what you're doing.
• add a variable ansible_python_interpreter: /opt/freeware/bin/python3 in your playbooks. This is my favourite way of solving the problem.
• add a global configuration interpreter_python = /opt/freeware/bin/python3 in /opt/freeware/etc/ansible/ansible.cfg on your Ansible controller node.

More about Python discovery in Ansible you can read here - https://docs.ansible.com/ansible/latest/reference_appendices/interpreter_discovery.html