>
> I now retriggered the job and it finished successfully.
>
Probably some other package got updates on resources in the meantime
which cause the repomd to be rebuilt.
> Last night I downloaded the files from resources.ovirt.org and from jenkins
> and compared them.
>
> cmp -l on them was very lo
I started getting Nagios alerts as the number of processes
on ovirt-srv06 was fluctuating around 450 which was the warning
threshold. Same story is happening happens on ovirt-srv05.
I've increased the threshold to 500 on these two hosts as
450 looks like a totally normal number of running proceses
> On Jun 23, 2016, at 9:30 AM, Barak Korren wrote:
>
>>
>> I now retriggered the job and it finished successfully.
>>
> Probably some other package got updates on resources in the meantime
> which cause the repomd to be rebuilt.
>
>> Last night I downloaded the files from resources.ovirt.org
eyal edri [Administrator] created OVIRT-607:
---
Summary: sort out jobs which didn't move to std ci
Key: OVIRT-607
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-607
Project: oVirt - virtual
The oVirt Project is pleased to announce today the general availability of
oVirt 4.0.0.
This release is available now for:
* Fedora 23 (tech preview)
* Red Hat Enterprise Linux 7.2 or later
* CentOS Linux (or similar) 7.2 or later
This release supports Hypervisor Hosts running:
* Red Hat Enterpri
Hello everyone,
I'll restart these two VMs to move them to the new oVirt cluster:
ci-templates-repo.phx.ovirt.org
glance.phx.ovirt.org
The first VM is used by lago. If any jobs fail
due to template unavailability please restart them.
If you find any persisting issues please let me know.
Regar
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
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
[
https://ovirt-jira.atlassian.net/browse/OVIRT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17507#comment-17507
]
eyal edri [Administrator] commented on OVIRT-608:
-
Some of the slaves are offli
Hi,
As part of an infrastructure upgrade, in approximately one hour at
01:00 AM TLV, http://jenkins.ovirt.org will be shut down for
maintenance, expected downtime is 15 minutes.
Patches sent during the downtime will be checked afterwards, patches
sent around 40 minutes prior to the downtime might n
[
https://ovirt-jira.atlassian.net/browse/OVIRT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508#comment-17508
]
Nadav Goldin commented on OVIRT-608:
During the evening I tried creating a snapshot of the
[
https://ovirt-jira.atlassian.net/browse/OVIRT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509#comment-17509
]
Nadav Goldin commented on OVIRT-608:
quick check - all disconnected VMs were disconnected o
Jenkins is back up to normal.
On Fri, Jun 24, 2016 at 12:07 AM, Nadav Goldin wrote:
> Hi,
> As part of an infrastructure upgrade, in approximately one hour at
> 01:00 AM TLV, http://jenkins.ovirt.org will be shut down for
> maintenance, expected downtime is 15 minutes.
> Patches sent during the
Hi Evgheni,
Unfortunately migrating the Jenkins VM failed, to (my) luck its back
running in the old Production cluster. so we could track this I am
listing again the steps taken today:
1. around 18:00 TLV time, I triggered a snapshot of the VM. This not
only failed but caused the Jenkins VM to be
14 matches
Mail list logo