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
can we close-wontfix this?
בתאריך 24 ביוני 2016 13:22, "Anton Marchukov (oVirt JIRA)" <
j...@ovirt-jira.atlassian.net> כתב:
>
> [
> https://ovirt-jira.atlassian.net/browse/OVIRT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Anton Marchukov reassigned
[
https://ovirt-jira.atlassian.net/browse/OVIRT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Marchukov reassigned OVIRT-608:
-
Assignee: Anton Marchukov (was: infra)
> [URGENT] Half of the Jenkins slaves are
[
https://ovirt-jira.atlassian.net/browse/OVIRT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17509#comment-17509
]
Nadav Goldin commented on OVIRT-608:
quick check - all disconnected VMs were disconnected on purpose to
[
https://ovirt-jira.atlassian.net/browse/OVIRT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508#comment-17508
]
Nadav Goldin commented on OVIRT-608:
During the evening I tried creating a snapshot of the Jenkins VM,
[
https://ovirt-jira.atlassian.net/browse/OVIRT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17507#comment-17507
]
eyal edri [Administrator] commented on OVIRT-608:
-
Some of the slaves are offline for a reason.
Some of the slaves are offline for a reason. We have storage overload that
can risk the stability of the entire DC, and until we won't move to use
local disk storage we can't keep all the slaves running all the time.
Having said that, if there something critical, we can start a few more
vms to
sbonazzo created OVIRT-608:
--
Summary: [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
