-
Notifications
You must be signed in to change notification settings - Fork 24.2k
Closed
Labels
affects_2.8This issue/PR affects Ansible v2.8This issue/PR affects Ansible v2.8bugThis issue/PR relates to a bug.This issue/PR relates to a bug.moduleThis issue/PR relates to a module.This issue/PR relates to a module.support:coreThis issue/PR relates to code supported by the Ansible Engineering Team.This issue/PR relates to code supported by the Ansible Engineering Team.tracebackThis issue/PR includes a traceback.This issue/PR includes a traceback.windowsWindows communityWindows community
Description
SUMMARY
When running our configuration script with Ansible v2..8 (devel branch) on 4 new Windows 10 laptops resulted in the below error:
TASK [Configure hostname, domain and workgroup] ********************************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: at <ScriptBlock>, <No file>: line 300
fatal: [computer113]: FAILED! => {"changed": false, "msg": "Unhandled exception while executing module: Skip computer 'computer113' with new name 'computer113' because the new name is the same as the current name."}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: at <ScriptBlock>, <No file>: line 300
fatal: [computer115]: FAILED! => {"changed": false, "msg": "Unhandled exception while executing module: Skip computer 'computer115' with new name 'computer115' because the new name is the same as the current name."}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: at <ScriptBlock>, <No file>: line 300
fatal: [computer116]: FAILED! => {"changed": false, "msg": "Unhandled exception while executing module: Skip computer 'computer116' with new name 'computer116' because the new name is the same as the current name."}
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: at <ScriptBlock>, <No file>: line 300
fatal: [computer114]: FAILED! => {"changed": false, "msg": "Unhandled exception while executing module: Skip computer 'computer114' with new name 'computer114' because the new name is the same as the current name."}
ISSUE TYPE
- Bug Report
COMPONENT NAME
win_domain_membership
ANSIBLE VERSION
ansible 2.8.0.dev0 (msc_user 91f86f51a6) last updated 2018/10/30 01:36:49 (GMT +200)
config file = /home/dag/home-made/crombeen/ansible.cfg
configured module search path = [u'/home/dag/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /opt/anvers/default/lib/ansible
executable location = /opt/anvers/default/bin/ansible
python version = 2.7.5 (default, May 31 2018, 09:41:32) [GCC 4.8.5 20150623 (Red Hat 4.8.5-28)]
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
affects_2.8This issue/PR affects Ansible v2.8This issue/PR affects Ansible v2.8bugThis issue/PR relates to a bug.This issue/PR relates to a bug.moduleThis issue/PR relates to a module.This issue/PR relates to a module.support:coreThis issue/PR relates to code supported by the Ansible Engineering Team.This issue/PR relates to code supported by the Ansible Engineering Team.tracebackThis issue/PR includes a traceback.This issue/PR includes a traceback.windowsWindows communityWindows community