# Problems with Solaris 8 & 9 in Ansible 2.2.0.0 **URL:** \ **Category:** Ansible Project\ **Created:** [November 15, 2016, 8:59am UTC](https://forum.ansible.com/t/problems-with-solaris-8-9-in-ansible-2-2-0-0/23025 "2016-11-15T08:59:12Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Daniel\_Delin](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@Daniel\_Delin](https://forum.ansible.com/u/Daniel_Delin)\ **Post date:** [November 15, 2016, 8:59am UTC](https://forum.ansible.com/t/problems-with-solaris-8-9-in-ansible-2-2-0-0/23025/1 "2016-11-15T08:59:12Z")
Just started testing the new 2.2 version with my current playbooks, but it fails already in the facts gathering on Solaris 8 and 9. Solaris 10 works fine, and 8 and 9 worked fine with 2.1.2.0 and 2.1.3.0. Python version is 2.6.2 on both Solaris 8 and 9. **Error message:** (2.2.0.0) -bash-4.2$ ansible-playbook --inventory-file=/local/ansible/unix/staging/inventory/hosts site.yml --limit xx.xx.xx.xx.xx -v Using /local/home/ans\_unix/.ansible.cfg as config file PLAY [First ansible tests] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* TASK [setup] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* fatal: [xx.xx.xx.xx.xx]: FAILED! =\> {“changed”: false, “cmd”: null, “failed”: true, “msg”: “Argument ‘args’ to run\_command must be list or string”, “rc”: 257} to retry, use: --limit @/local/ansible/unix/staging/site.retry PLAY RECAP \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* xx.xx.xx.xx.xx : ok=0 changed=0 unreachable=0 failed=1 Anyone else seen this ? ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [November 15, 2016, 3:11pm UTC](https://forum.ansible.com/t/problems-with-solaris-8-9-in-ansible-2-2-0-0/23025/2 "2016-11-15T15:11:33Z")
can you show the output when using -vvvv? ---
**Author:** ![Daniel\_Delin](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@Daniel\_Delin](https://forum.ansible.com/u/Daniel_Delin)\ **Post date:** [November 16, 2016, 10:00am UTC](https://forum.ansible.com/t/problems-with-solaris-8-9-in-ansible-2-2-0-0/23025/3 "2016-11-16T10:00:28Z")
Using /local/home/ans\_unix/.ansible.cfg as config file statically included: /local/ansible/unix/staging/roles/test/tasks/test\_replace.yml statically included: /local/ansible/unix/staging/roles/test/tasks/test\_blockinfile.yml Loading callback plugin default of type stdout, v2.0 from /local/ansible/install/2.2.0.0/lib/python2.7/site-packages/ansible/plugins/callback/ **init**.pyc PLAYBOOK: site.yml \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* 1 plays in site.yml PLAY [First ansible tests] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* TASK [setup] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* Using module file /local/ansible/install/2.2.0.0/lib/python2.7/site-packages/ansible/modules/core/system/setup.py \ ESTABLISH SSH CONNECTION FOR USER: root \ SSH: EXEC ssh -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=root -o ConnectTimeout=10 -o ControlPath=/local/home/ans\_unix/.ansible/cp/ansible-ssh-%h-%p-%r xx.xx.xx.xx ‘/bin/sh -c ‘"’"’( umask 77 && mkdir -p “`echo $HOME/.ansible/tmp/ansible-tmp-1479290147.18-43117107564303`” && echo ansible-tmp-1479290147.18-43117107564303=“`echo $HOME/.ansible/tmp/ansible-tmp-1479290147.18-43117107564303`” ) && sleep 0’“'”‘’ \ PUT /tmp/tmp8eXZ2E TO //.ansible/tmp/ansible-tmp-1479290147.18-43117107564303/setup.py \ SSH: EXEC sftp -b - -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=root -o ConnectTimeout=10 -o ControlPath=/local/home/ans\_unix/.ansible/cp/ansible-ssh-%h-%p-%r ‘[xx.xx.xx.xx]’ \ ESTABLISH SSH CONNECTION FOR USER: root \ SSH: EXEC ssh -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=root -o ConnectTimeout=10 -o ControlPath=/local/home/ans\_unix/.ansible/cp/ansible-ssh-%h-%p-%r xx.xx.xx.xx ‘/bin/sh -c ‘"’“‘chmod u+x //.ansible/tmp/ansible-tmp-1479290147.18-43117107564303/ //.ansible/tmp/ansible-tmp-1479290147.18-43117107564303/setup.py && sleep 0’”’“‘’ \ ESTABLISH SSH CONNECTION FOR USER: root \ SSH: EXEC ssh -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=root -o ConnectTimeout=10 -o ControlPath=/local/home/ans\_unix/.ansible/cp/ansible-ssh-%h-%p-%r -tt xx.xx.xx.xx '/bin/sh -c '”‘"’/local/ansible/bin/python //.ansible/tmp/ansible-tmp-1479290147.18-43117107564303/setup.py; rm -rf “//.ansible/tmp/ansible-tmp-1479290147.18-43117107564303/” \> /dev/null 2\>&1 && sleep 0’“'”‘’ fatal: [xx.xx.xx.xx]: FAILED! =\> { “changed”: false, “cmd”: null, “failed”: true, “invocation”: { “module\_args”: { “fact\_path”: “/etc/ansible/facts.d”, “filter”: “\*”, “gather\_subset”: [ “all” ], “gather\_timeout”: 10 }, “module\_name”: “setup” }, “msg”: “Argument ‘args’ to run\_command must be list or string”, “rc”: 257 } to retry, use: --limit @/local/ansible/unix/staging/site.retry PLAY RECAP \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\* xx.xx.xx.xx : ok=0 changed=0 unreachable=0 failed=1 ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [November 17, 2016, 1:32am UTC](https://forum.ansible.com/t/problems-with-solaris-8-9-in-ansible-2-2-0-0/23025/4 "2016-11-17T01:32:06Z")
Weird, for some reason it is trying to run a ‘null’ command. I need to narrow it down, can you run ansible with ANSIBLE\_DEBUG=1 and then look at the target machine’s syslog (it should log every run\_command). ---
**Author:** ![Daniel\_Delin](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@Daniel\_Delin](https://forum.ansible.com/u/Daniel_Delin)\ **Post date:** [November 17, 2016, 11:43am UTC](https://forum.ansible.com/t/problems-with-solaris-8-9-in-ansible-2-2-0-0/23025/5 "2016-11-17T11:43:08Z")
Trying with ANSIBLE\_DEBUG=1 doesn´t produce anything in the syslog on the Solaris target machine. I also tried with a known working Linux machine, and there it prints all the commands in the syslog. ---
**Author:** ![Daniel\_Delin](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@Daniel\_Delin](https://forum.ansible.com/u/Daniel_Delin)\ **Post date:** [November 17, 2016, 1:04pm UTC](https://forum.ansible.com/t/problems-with-solaris-8-9-in-ansible-2-2-0-0/23025/6 "2016-11-17T13:04:44Z")
Maybe I should also have mentioned that both Solaris machines are branded zones, if that matters. ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [November 29, 2016, 6:31pm UTC](https://forum.ansible.com/t/problems-with-solaris-8-9-in-ansible-2-2-0-0/23025/7 "2016-11-29T18:31:13Z")
Ansible just uses python’s syslog library, if that does not work in the solaris branded zones … not sure what to do at this point. ---
**Author:** ![Daniel\_Delin](https://avatars.discourse-cdn.com/v4/letter/d/d78d45/32.png) [@Daniel\_Delin](https://forum.ansible.com/u/Daniel_Delin)\ **Post date:** [December 5, 2016, 12:24pm UTC](https://forum.ansible.com/t/problems-with-solaris-8-9-in-ansible-2-2-0-0/23025/8 "2016-12-05T12:24:27Z")
Also tested on a bare metal Solaris 8 machine, and it has the same problems, so it does not seem to be related to the zones. Maybe I should file a proper bug report, but since I´m new to Ansible I want to rule out my incompetence as the cause first.