We’re new to AWX. We set it up in containers and it was running well against our Windows servers. Then we had an issue where something got corrupt so we rebuilt the containers and started over. Now when I try to run my Windows playbook the following error gets thrown:
{
“msg”: “Unexpected failure during module execution.”,
“exception”: “Traceback (most recent call last):\n File "/usr/lib/python2.7/site-packages/ansible/executor/task_executor.py", line 144, in run\n res = self._execute()\n File "/usr/lib/python2.7/site-packages/ansible/executor/task_executor.py", line 648, in _execute\n result = self._handler.run(task_vars=variables)\n File "/usr/lib/python2.7/site-packages/ansible/plugins/action/normal.py", line 46, in run\n result = merge_hash(result, self._execute_module(task_vars=task_vars, wrap_async=wrap_async))\n File "/usr/lib/python2.7/site-packages/ansible/plugins/action/init.py", line 917, in _execute_module\n res = self._low_level_execute_command(cmd, sudoable=sudoable, in_data=in_data)\n File "/usr/lib/python2.7/site-packages/ansible/plugins/action/init.py", line 1042, in _low_level_execute_command\n cmd = self._connection.become.build_become_command(cmd, self._connection._shell)\n File "/usr/lib/python2.7/site-packages/ansible/plugins/become/sudo.py", line 104, in build_become_command\n return ’ ‘.join([becomecmd, flags, prompt, user, self._build_success_command(cmd, shell)])\n File "/usr/lib/python2.7/site-packages/ansible/plugins/become/init.py", line 52, in _build_success_command\n cmd = shlex_quote(’%s %s %s %s’ % (shell.ECHO, self.success, shell.COMMAND_SEP, cmd))\nAttributeError: ‘ShellModule’ object has no attribute ‘ECHO’\n”,
“_ansible_no_log”: false,
“stdout”: “”
}
We can still run playbooks against Linux servers. It almost seems like it’s having trouble running the Windows modules? We reproduced all the setup that was necessary to connect to Windows over WinRM. If I execute a win_ping under Inventories, I get a successful Pong back.
As a test, I logged onto the Task and Web containers to see if I could manually run a playbook from the command line against a Windows server and that ran fine so it seems to be AWX specific.
Our Ansible and AWX knowlege is limited so any help on this would be greatly appreciated if anyone has seen this before.
Matt