FYI:
https://groups.google.com/forum/#!topic/ansible-project/Mj6vmhqMED8
just beware before you do "yum upgrade".
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
___
infrastructure mailing list
infrastr
On Wed, 26 Feb 2014 13:45:56 +0100
Miroslav Suchý wrote:
> FYI:
> https://groups.google.com/forum/#!topic/ansible-project/Mj6vmhqMED8
>
> just beware before you do "yum upgrade".
I'd be interested in short reproducers here... the changes between
1.4.3 and 1.4.5 are really minor:
1.4.5 "Could T
On 02/27/2014 12:21 AM, Kevin Fenzi wrote:
I'd be interested in short reproducers here... the changes between
1.4.3 and 1.4.5 are really minor:
That is really strange. The problem disappear after I downgraded. I was not able to reproduce it on another machine. And
today it start happen on copr
It happen again.But now I have more traces and hints.
This morning (9:33 UTC) I get Nagios alert that:
WARN: datanommer has not seen a copr message in 6 hours, 10 minutes, 39 seconds
which means that sometime between 3:30 UTC and 4:30 UTC something happen.
I logged to copr-be and to my surprise
On Fri, 28 Feb 2014 11:15:00 +0100
Miroslav Suchý wrote:
> It happen again.But now I have more traces and hints.
...snip...
> I am not sure about the first one.
>
> The second one is some ansible playbook (can it be that nirik check
> of differences?) But I'm really clueless how it can
> remov
On 02/28/2014 06:52 PM, Kevin Fenzi wrote:
Just ping me on irc when you are available to watch the copr-be end.
Will do.
In the meantime I 'solved' it by "chattr +i" on those files.
--
Miroslav Suchy, RHCE, RHCDS
Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys
On Mon, 03 Mar 2014 08:42:50 +0100
Miroslav Suchý wrote:
> On 02/28/2014 06:52 PM, Kevin Fenzi wrote:
> > Just ping me on irc when you are available to watch the copr-be end.
>
> Will do.
>
> In the meantime I 'solved' it by "chattr +i" on those files.
:)
I did look at this this weekend and
