Hello Sandro.

I believe we have "agent install" in post build actions, so this failure happens only in the cases when for some reason the post build actions are not executed at all and there is hardly we can do anything by jenkins means.

When we are going to roll over our new ovirt pool based slaves this problem should go away as we will be rotating slaves to completely new ones.

Anton.

On Thu, Apr 7, 2016 at 8:55 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:

Il 07/Apr/2016 16:43, "Anton Marchukov" <amarchuk@redhat.com> ha scritto:
>
> Hello Shlomi.
>
> I do not see we should have any slaves with puppet disabled. Afaik this is being disabled by job during it run to prevent some mock yum conflicts, but then if everything is ok the job should restore it. Sometimes it does not happen....

Can you add to cleanup scripts a check on the agent status and start if down?

>
> Anton.
>
> On Thu, Apr 7, 2016 at 4:21 PM, Shlomi Ben David <sbendavi@redhat.com> wrote:
>>
>> Hi,
>>
>> On the following host: el6-vm10.phx.ovirt.org the puppet agent is disabled.
>> Is anybody know if it disabled for a reason?
>>
>> Thanks in advanced,
>>
>> --
>> Shlomi Ben-David | Software Engineer | Red Hat ISRAEL
>> Phone: +972-54-8008858
>> IRC: sbendavi
>>
>> OPEN SOURCE - 1 4 011 && 011 4 1
>>
>>
>> _______________________________________________
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>
>
>
> --
> Anton Marchukov
> Senior Software Engineer - RHEV CI - Red Hat
>
>
> _______________________________________________
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>

--

Anton Marchukov
Senior Software Engineer - RHEV CI - Red Hat