The slaves are not down as a result of a problem or need, it was intentional to reduce load. Once we resolve the storage issues with the hooks we can load back more slaves, but its not URGENT or indicates of a specific problem with slaves. We can keep it if we want a reminder to bring up all slaves once we fix the storage load, but we have other tickets for it, so i guess this is duplicate. On Fri, Jun 24, 2016 at 11:26 PM, Barak Korren <bkorren@redhat.com> wrote:

can we close-wontfix this? בתאריך 24 ביוני 2016 13:22,‏ "Anton Marchukov (oVirt JIRA)" < jira@ovirt-jira.atlassian.net> כתב:

...

[ https://ovirt-jira.atlassian.net/browse/OVIRT-608?page=com.atlassian.jira.pl... ]

Anton Marchukov reassigned OVIRT-608: -------------------------------------

Assignee: Anton Marchukov (was: infra)

...

[URGENT] Half of the Jenkins slaves are offline -----------------------------------------------

Key: OVIRT-608 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-608 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: Anton Marchukov

Please check what happened, 24 jenkins slaves are down right now. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community

collaboration. > See how it works at redhat.com

-- This message was sent by Atlassian JIRA (v1000.98.4#100004) _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

-- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)