Re: Something is polluting lockbox01 /

2014-10-09 Thread Kevin Fenzi
On Wed, 08 Oct 2014 15:33:14 +0200 Miroslav Suchý msu...@redhat.com wrote: On 09/17/2014 05:18 PM, Kevin Fenzi wrote: Yes, ansible makes these anytime a playbook has failed hosts. The idea is that you can then pass this retry to it on the next run and it will only run on those hosts that

Re: Something is polluting lockbox01 /

2014-10-08 Thread Miroslav Suchý
On 09/17/2014 05:18 PM, Kevin Fenzi wrote: Yes, ansible makes these anytime a playbook has failed hosts. The idea is that you can then pass this retry to it on the next run and it will only run on those hosts that failed.;) There shouldn't be any in / they should be in/root/ I guess ('cos of

Re: Something is polluting lockbox01 /

2014-09-17 Thread Kevin Fenzi
On Tue, 16 Sep 2014 16:41:16 -0400 Ralph Bean rb...@redhat.com wrote: On Tue, Sep 16, 2014 at 02:14:06PM -0600, Stephen John Smoogen wrote: Anyone know what this is? I think ansible leaves .retry files around (but I haven't been able to find documentation directly about them). Yes,

Re: Something is polluting lockbox01 /

2014-09-16 Thread Till Maas
On Tue, Sep 16, 2014 at 02:14:06PM -0600, Stephen John Smoogen wrote: So I feel bad.. I didn't see this til today and its been going on for a while. Some script is putting a lot of file entries in / versus where-ever it is supposed to do so. The entries will be something.retry Anyone know

Re: Something is polluting lockbox01 /

2014-09-16 Thread Ralph Bean
On Tue, Sep 16, 2014 at 02:14:06PM -0600, Stephen John Smoogen wrote: Anyone know what this is? I think ansible leaves .retry files around (but I haven't been able to find documentation directly about them). pgpar0N43kGXR.pgp Description: PGP signature