I understand a lot of what happened here. I’ll be digesting it for a while. Thank you so much for taking the time to create this config, and helping me understand why the train was going off the rails at so many points.
Key takeway is to look for a truly appropriate base image, that’s fully feature-complete, before diving down the rabbit hole of trying to layer goodness onto a deprecated or bare image. That makes good sense. Thank you.
Stdout
ansible-playbook [core 2.15.9]
config file = None
configured module search path = ['/runner/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python3.9/site-packages/ansible
ansible collection location = /runner/requirements_collections:/runner/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/local/bin/ansible-playbook
python version = 3.9.18 (main, Jan 4 2024, 00:00:00) [GCC 11.4.1 20231218 (Red Hat 11.4.1-3)] (/usr/bin/python3)
jinja version = 3.1.3
libyaml = True
No config file found; using defaults
host_list declined parsing /runner/inventory/hosts as it did not pass its verify_file() method
Parsed /runner/inventory/hosts inventory source with script plugin
Skipping callback 'awx_display', as we already have a stdout callback.
Skipping callback 'default', as we already have a stdout callback.
Skipping callback 'minimal', as we already have a stdout callback.
Skipping callback 'oneline', as we already have a stdout callback.
PLAYBOOK: win_ping.yml *********************************************************
1 plays in ansible/playbooks/demos/win_ping.yml
PLAY [all] *********************************************************************
TASK [ansible.windows.win_ping] ************************************************
task path: /runner/project/ansible/playbooks/demos/win_ping.yml:6
task path: /runner/project/ansible/playbooks/demos/win_ping.yml:6
Using module file /runner/requirements_collections/ansible_collections/ansible/windows/plugins/modules/win_ping.ps1
Pipelining is enabled.
<server1> ESTABLISH WINRM CONNECTION FOR USER: user1@domain on PORT 5986 TO server1
EXEC (via pipeline wrapper)
ok: [server1] => {
"changed": false,
"invocation": {
"module_args": {
"data": "pong"
}
},
"ping": "pong"
}
PLAY RECAP *********************************************************************
server1 : ok=1 changed=0 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0