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
-rw-r--r--. 1 root root 36 Sep 16 04:28 fed-cloud09.cloud.fedoraproject.org.retry -rw-r--r--. 1 root root 68 Jul 24 07:54 fedimg.retry -rw-r--r--. 1 root root 106 Jun 17 04:29 fedoauth.retry -rw-r--r--. 1 root root 16 Aug 19 04:09 fedocal.dev.fedoraproject.org.retry -rw-r--r--. 1 root root 103 Jun 17 04:26 fedocal.retry -rw-r--r--. 1 root root 37 Jul 27 05:53 gallery.retry -rw-r--r--. 1 root root 43 Jun 17 04:11 github2fedmsg.retry -rw-r--r--. 1 root root 28 Sep 16 04:23 hrf.cloud.fedoraproject.org.retry -rw-r--r--. 1 root root 16 Aug 31 11:44 jenkins-cloud.retry -rw-r--r--. 1 root root 36 Jul 2 14:05 kerneltest.retry -rw-r--r--. 1 root root 50 Aug 16 07:14 keyserver.retry -rw-r--r--. 1 root root 34 Jun 17 04:30 koji-hub.retry -rw-r--r--. 1 root root 32 Aug 26 04:18 koschei.cloud.fedoraproject.org.retry -rw-r--r--. 1 root root 34 Aug 19 04:07 lists-dev.cloud.fedoraproject.org.retry -rw-r--r--. 1 root root 36 Sep 16 08:21 lockbox.retry -rw-r--r--. 1 root root 29 Jul 23 04:04 logserver.retry -rw-r--r--. 1 root root 16 Aug 19 04:08 logstash-dev.cloud.fedoraproject.org.retry -rw-r--r--. 1 root root 66 Jul 1 04:11 mailman.retry -rw-r--r--. 1 root root 41 Sep 3 10:39 mirrorlist.retry -rw-r--r--. 1 root root 29 Jul 10 05:02 nagios_phx2.retry -rw-r--r--. 1 root root 24 Sep 9 07:45 noc.retry -rw-r--r--. 1 root root 84 Jul 18 07:02 notifs-backend.retry -rw-r--r--. 1 root root 152 Jun 17 04:30 notifs-web.retry -rw-r--r--. 1 root root 144 Jun 17 04:29 nuancier.retry -rw-r--r--. 1 root root 106 Aug 2 09:57 packages.retry -rw-r--r--. 1 root root 97 Jul 23 07:26 paste.retry -rw-r--r--. 1 root root 97 Jun 17 04:30 pkgdb.retry -rw-r--r--. 1 root root 68 Jun 17 04:26 postgresl-server.retry -rw-r--r--. 1 root root 33 Aug 17 07:47 qadevel-stg.retry -rw-r--r--. 1 root root 32 Jun 17 04:26 releng.retry -rw-r--r--. 1 root root 37 Aug 7 11:00 resultsdb-dev.retry -rw-r--r--. 1 root root 33 Sep 16 07:19 resultsdb-prod.retry -rw-r--r--. 1 root root 37 Sep 4 05:01 resultsdb-stg.retry -rw-r--r--. 1 root root 16 Aug 19 04:06 shogun-ca.cloud.fedoraproject.org.retry -rw-r--r--. 1 root root 34 Jul 9 07:08 smtp-mm.retry -rw-r--r--. 1 root root 76 Jul 18 06:57 summershum.retry -rw-r--r--. 1 root root 72 Aug 7 09:48 sundries.retry -rw-r--r--. 1 root root 100 Jun 17 04:41 tagger.retry -rw-r--r--. 1 root root 160 Jul 23 05:30 taskotron-dev-clients.retry -rw-r--r--. 1 root root 37 Jul 23 09:54 taskotron-dev.retry -rw-r--r--. 1 root root 160 Jul 23 04:34 taskotron-prod-clients.retry -rw-r--r--. 1 root root 33 Sep 16 07:27 taskotron-prod.retry -rw-r--r--. 1 root root 40 Sep 12 05:21 taskotron-stg-clients.retry -rw-r--r--. 1 root root 37 Jul 23 05:07 taskotron-stg.retry -rw-r--r--. 1 root root 37 Jun 19 14:13 taskotron.retry -rw-r--r--. 1 root root 34 Jul 1 07:20 unbound.retry -rw-r--r--. 1 root root 66 Jun 17 04:27 value.retry -rw-r--r--. 1 root root 37 Sep 16 13:19 virthost.retry -rw-r--r--. 1 root root 30 Jul 24 04:40 wiki.retry
Anyone know what this is?
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 what this is?
Ansible creates these files, usually in the users home directory.
Regards Till
On Tue, 16 Sep 2014 16:41:16 -0400 Ralph Bean rbean@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, 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/
and it should be safe to remove them all.
kevin
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 fed-cloud09.cloud.fedoraproject.org.retry) that rbac likely change $HOME and it land in / instead of home or /tmp.
On Wed, 08 Oct 2014 15:33:14 +0200 Miroslav Suchý msuchy@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 failed.;)
There shouldn't be any in / they should be in/root/
I guess ('cos of fed-cloud09.cloud.fedoraproject.org.retry) that rbac likely change $HOME and it land in / instead of home or /tmp.
Could be the case.
We should really land tflinks rbac-playbook re-write before next freeze (and make sure this is fixed there too)
kevin
infrastructure@lists.fedoraproject.org