When I run the playbook on a RHEL8.1 server Iin the Alias lab, I get this error below, but I never used to get it with RHEL8.0. There is no python installed, either 2 or 3. This breaks my automation and makes me do everything by hand. Is there some way for ansible-playbook to avoid running python to do this and just give me password-less ssh access using the raw module? Once I have that, I can do whatever commands are needed to further initialize the system from there.
Suggestion: have the user specify the public key file to install, and just make ~/.ssh/authorized_keys equal to that using the raw module, and do nothing else. Since we got the error below, ansible-playbook got into the system! So it would work.
MSG:
The following modules failed to execute: setup
fatal: [e23-h17-740xd.alias.example]: FAILED! => {
"ansible_facts": {},
"changed": false,
"failed_modules": {
"setup": {
"failed": true,
"module_stderr": "Shared connection to e23-h17-740xd.alias.example.com closed.\r\n",
"module_stdout": "/bin/sh: /usr/bin/python: No such file or directory\r\n",
"msg": "The module failed to execute correctly, you probably need to set the interpreter.\nSee stdout/stderr for the exact error",
"rc": 127
}
}
[root@e23-h15-740xd ~]# which python
/usr/bin/which: no python in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)