Thanks, installed the kinit command, but now getting this error:
TASK [windowsupdates : Check If Windows Updates are Available]
******************************************************************************************************************************************************************
task path: /etc/ansible/roles/windowsupdates/tasks/main.yml:1
The full traceback is:
Traceback (most recent call last):
File
"/root/.ansible/collections/ansible_collections/ansible/windows/plugins/action/win_updates.py",
line 761, in run
result = self._run_sync(task_vars, module_options, reboot,
reboot_timeout)
File
"/root/.ansible/collections/ansible_collections/ansible/windows/plugins/action/win_updates.py",
line 834, in _run_sync
update_result = self._run_updates(task_vars, module_options,
poll_script_path, cancel_script_path)
File
"/root/.ansible/collections/ansible_collections/ansible/windows/plugins/action/win_updates.py",
line 907, in _run_updates
output_path, task_pid, cancel_id = self._start_updates(task_vars,
module_options)
File
"/root/.ansible/collections/ansible_collections/ansible/windows/plugins/action/win_updates.py",
line 951, in _start_updates
raise _ReturnResultException(msg, exception=result.get('exception',
None))
ansible_collections.ansible.windows.plugins.action.win_updates._ReturnResultException:
MODULE FAILURE
See stdout/stderr for the exact error
fatal: [ansible_host=x.x.x.x]: FAILED! => {
"changed": false,
"failed_update_count": 0,
"filtered_updates": {},
"found_update_count": 0,
"installed_update_count": 0,
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
"updates": {}
}
...ignoring
The full traceback is:
Traceback (most recent call last):
File
"/root/.ansible/collections/ansible_collections/ansible/windows/plugins/action/win_updates.py",
line 761, in run
result = self._run_sync(task_vars, module_options, reboot,
reboot_timeout)
File
"/root/.ansible/collections/ansible_collections/ansible/windows/plugins/action/win_updates.py",
line 834, in _run_sync
update_result = self._run_updates(task_vars, module_options,
poll_script_path, cancel_script_path)
File
"/root/.ansible/collections/ansible_collections/ansible/windows/plugins/action/win_updates.py",
line 907, in _run_updates
output_path, task_pid, cancel_id = self._start_updates(task_vars,
module_options)
File
"/root/.ansible/collections/ansible_collections/ansible/windows/plugins/action/win_updates.py",
line 951, in _start_updates
raise _ReturnResultException(msg, exception=result.get('exception',
None))
ansible_collections.ansible.windows.plugins.action.win_updates._ReturnResultException:
MODULE FAILURE
See stdout/stderr for the exact error
fatal: [ansible_host=x.x.x.x]: FAILED! => {
"changed": false,
"failed_update_count": 0,
"filtered_updates": {},
"found_update_count": 0,
"installed_update_count": 0,
"msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
"updates": {}
}
...ignoring
The same playbook works when using the basic authentication:
TASK [windowsupdates : Check If Windows Updates are Available]
******************************************************************************************************************************************************************
task path: /etc/ansible/roles/windowsupdates/tasks/main.yml:1
ok: [hostname] => {
"changed": false,
"failed_update_count": 0,
"filtered_updates": {},
"found_update_count": 0,
"installed_update_count": 0,
"invocation": {
"module_args": {
"accept_list": null,
"category_names": [
"Application",
"Connectors",
"DefinitionUpdates",
"FeaturePacks",
"Guidance",
"ServicePacks",
"Tools",
"UpdateRollups",
"CriticalUpdates",
"SecurityUpdates",
"Drivers",
"Updates"
],
"log_path": "C:\\ansible_wu.txt",
"reboot": false,
"reboot_timeout": 1200,
"reject_list": null,
"server_selection": "managed_server",
"skip_optional": false,
"state": "searched",
"use_scheduled_task": false
}
},
"reboot_required": false,
"updates": {}
}
On Tuesday, August 16, 2022 at 10:50:48 AM UTC-5 [email protected] wrote:
> Your answer is in the error message.
>
> "Kerberos auth failure when calling kinit cmd 'kinit': *The command was
> not found or was not executable: kinit.*"
>
> --
> Walter Rowe, Chief
> Infrastructure Services
> Office of Information Systems Management
> National Institute of Standards and Technology
> United States Department of Commerce
>
> On Tuesday, August 16, 2022 at 11:13:53 AM UTC-4 Nitrous wrote:
>
>> Our ansible box isnt domain joined, and we build alot of VMs from a
>> template, that has an account part of the image, that is local admin.
>>
>> I was reading more into kerboros authentication, and setup my var file as
>> this:
>>
>> [xx:vars]
>> ansible_connection=winrm
>> ansible_user=xx
>> ansible_password=xx
>> ansible_port=5986
>> ansible_ssh_port=5986
>> ansible_winrm_transport=kerberos
>> ansible_winrm_scheme=https
>> ansible_winrm_server_cert_validation=ignore
>> domain_server=test.local
>> domain_username=cc
>> domain_password=cc
>> wsus_server=cc
>>
>> When I run my playbook, I get:
>> fatal: [x.x.x.x]: UNREACHABLE! => {
>> "changed": false,
>> "msg": "Kerberos auth failure when calling kinit cmd 'kinit': The
>> command was not found or was not executable: kinit.",
>> "unreachable": true
>> }
>>
>> My host file has the sever entry as below:
>>
>> hostname ansible_host=IP address of host
>>
>> Changing the ansible_winrm_transport to basic works, with no issue.
>>
>> How can I use my existing config to work with kerberos?
>>
>> Please help/Suggest?
>>
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/8efff905-6e65-4b3d-bcd1-f1157c22daccn%40googlegroups.com.
