Yes, please let us know if it does. I'm pushing for 1.5 to release a bit sooner (weeks) actually.
I'd be interested in the remote OS and conditions that triggered this situation. On Wed, Feb 19, 2014 at 7:22 AM, Matt Martz <[email protected]> wrote: > Marc, > > I do believe this issue has been resolved in 1.5 (devel). 1.5 is > tentatively scheduled to release sometime within the next month, but should > be stable enough to use currently. > > You may want to give it a try and see how it works. > > > On Wednesday, February 19, 2014, Marc Patermann < > [email protected]> wrote: > >> Hi, >> Marc Patermann schrieb (19.02.2014 09:47 Uhr): >> >>> I added about 70 (mostly?) identical servers to my inventory. On two I >>> get this error: >>> >>> # ansible -m setup -i produktion paps077* >>> paps077.example.com | FAILED >> { >>> "failed": true, >>> "msg": "Traceback (most recent call last):\n File >>> \"/home/foo/.ansible/tmp/ansible-1392799041.61-199234546100736/setup\", >>> line 3228, in ?\n main()\n File \"/home/foo/.ansible/tmp/ >>> ansible-1392799041.61-199234546100736/setup\", line 2199, in main\n >>> data = run_setup(module)\n File \"/home/foo/.ansible/tmp/ >>> ansible-1392799041.61-199234546100736/setup\", line 2140, in >>> run_setup\n facts = ansible_facts()\n File \"/home/foo/.ansible/tmp/ >>> ansible-1392799041.61-199234546100736/setup\", line 2129, in >>> ansible_facts\n facts.update(Facts().populate())\n File >>> \"/home/foo/.ansible/tmp/ansible-1392799041.61-199234546100736/setup\", >>> line 143, in __init__\n self.get_cmdline()\n File >>> \"/home/foo/.ansible/tmp/ansible-1392799041.61-199234546100736/setup\", >>> line 338, in get_cmdline\n for piece in shlex.split(data):\n File >>> \"/usr/lib64/python2.4/shlex.py\", line 279, in split\n return >>> list(lex)\n File \"/usr/lib64/python2.4/shlex.py\", line 269, in >>> next\n token = self.get_token()\n File >>> \"/usr/lib64/python2.4/shlex.py\", >>> line 96, in get_token\n raw = self.read_token()\n File >>> \"/usr/lib64/python2.4/shlex.py\", line 191, in read_token\n raise >>> ValueError, \"No escaped character\"\nValueError: No escaped character\n", >>> "parsed": false >>> } >>> >>> Ansible is 1.4.1. >>> >> I updated to 1.4.4 with no success and then built 1.4.5 - but this does >> not help as well. >> >> What caused this and how to solve this? >>> These are SLES 10 SP 2 Servers, but the other 68 are too. >>> >> >> Marc >> >> -- >> 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 post to this group, send email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > -- > Matt Martz > [email protected] > http://sivel.net/ > > -- > 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 post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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 post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
