[ansible-project] cannot stat command with * and `

I am trying to rename folder that is unpacked. So I can only get file name accurately with grep (or some sort of regex expression) via ansible, the following command fails with the error message: stderr: mv: cannot stat `/var/www/`ls /var/www/ | grep client`': No such file or directory command

Re: [ansible-project] lineinfile task that spans multiple lines

Is there any way to make lineinfile work with Python's multiline regex (like /pattern/s)? lineinfile makes the idempotence a bit easier than grep/sed. But I'll go that route if need be. Usually, I just use a template file anyways, but for this particular file, there are just three lines that ne

[ansible-project] Re: cobbler external inventory script, does not seem to pick up the already existing hosts in cobbler

Hi Joost, I just spent some time digging for the same. Turns out that my existing systems did not have "management" set and were therefore not included in the results. Should this be the case, you should start getting output after issuing one of these: # cobbler system edit --name=somenode --m

Re: [ansible-project] Should move shell module from sh to bash?

The /bin/sh can be very different shells on diff platforms, when linked to bash it is very forgiving about bashisms in posix sh, but other shells are not. If you are using bash shell syntax, point at bash, not sh, to avoid these errors. -- You received this message because you are subscribed to t

Re: [ansible-project] Handlers and failures

Currently the retry mechanism is an inventory file, so likely not. The mechanism suggested before is a "force handlers" flag to be used with the option. --Michael On Sat, Feb 8, 2014 at 7:36 PM, Brent Langston wrote: > What if you just abort the remaining tasks, and still run the handlers > th

Re: [ansible-project] Handlers and failures

What if you just abort the remaining tasks, and still run the handlers that have already been set on that run? Brent On Sat, Feb 8, 2014 at 7:34 PM, James Martin wrote: > I wonder if ansible's retry feature could be made smart enough to note the > handlers that were notified

Re: [ansible-project] Handlers and failures

I wonder if ansible's retry feature could be made smart enough to note the handlers that were notified but not executed. Then on the subsequent run, those handlers would get executed. - James On Fri, Feb 7, 2014 at 12:51 PM, Nadav Samet wrote: > Hey, > > I have a play where I make edits to apa

Re: [ansible-project] Handlers and failures

Here's an example of the scenario I am describing: - handlers: -name: restart apache -service: apache state=restarted - tasks: - name: enable apache proxy module [A] command; a2enmod proxy creates=/etc/apache/mods-ehabled/proxy.load notify: restart apache - name: task that may

Re: [ansible-project] Apache Libcloud looks interesting

Yep. Our policy is to use the native bindings for a particular provider whenever available to expose the maximum number of knobs and switches. libcloud works when something else better doesn't exist in Python, or if that's the primary way the community around that particular provider does things.

[ansible-project] Should move shell module from sh to bash?

Unless I'm missing something, can't you just set executable: /bin/bash ? -- 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 ansible-project+unsubscr...@googlegro

[ansible-project] Should move shell module from sh to bash?

Hi, Refer to shell module doc , current it use /bin/sh to execute shell command, most time it works fine, but for following example, the result from Ubuntu is different. - shell: command -v nwef Since in Ubuntu, /bin/sh -> dash, the command will r

Re: [ansible-project] Re: Get rid of "previous known host file not found"

How do I know what they should be? On Saturday, February 8, 2014 6:39:21 AM UTC+7, Jesse Keating wrote: > > On 2/7/14, 1:13 PM, Ilya Ivanov wrote: > > So what can I do to finally find the previous host file? > > If you can reliably repeatably reproduce this, do the run with - to > make sure