Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/1651/
Build Number: 1651
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51727
### Logwatch 7.3.6 (05/19/07)
Processing Initiated: Wed Jan 13 03:19:19 2016
Date Range Processed: yesterday
( 2016-Jan-12 )
Period is day.
Detail Level of Output: 0
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/1742/
Build Number: 1742
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/5176
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/1652/
Build Number: 1652
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51761
My question was why do we need the build artifacts for e.g?
I'm OK with the check-patch jobs that verify compilation for e.g, but are
we using the 3.6.2 build artifacts jobs?
e.
On Wed, Jan 13, 2016 at 9:59 AM, Sandro Bonazzola
wrote:
>
>
> On Wed, Jan 13, 2016 at 8:22 AM, Eyal Edri wrote:
>
>
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/1743/
Build Number: 1743
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/5162
Project:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/770/
Build Number: 770
Build Status: Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51660
--
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/1653/
Build Number: 1653
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51627
Great :)
I'll track it for a few days to see its all good and update our wiki
pages/mirror list afterwards.
thanks,
Nadav.
On Tue, Jan 12, 2016 at 11:04 AM, Lior Kaplan wrote:
> Bingo (:
>
> http://mirror.isoc.org.il/pub/ovirt/
>
>
> I'll set a daily update.
>
> Kaplan
>
> On Mon, Jan 11, 2016
Title: Message Title
eyal edri [Administra
I have just submitted a set of 4 patches where 1 patch unit tests failed with
the pasted text below. Those patches are absolutely unrelated to those failures.
Please check into those issues - Thanks
http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc23-x86_64/2168/console
12:15:21
12:15:
Project:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/771/
Build Number: 771
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51723
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/1745/
Build Number: 1745
Build Status: Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51628
---
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_merged/1744/
Build Number: 1744
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/5171
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/1654/
Build Number: 1654
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51714
Title: Message Title
bkorren commented on
> On Jan 13, 2016, at 1:20 PM, Vinzenz Feenstra wrote:
>
> I have just submitted a set of 4 patches where 1 patch unit tests failed with
> the pasted text below. Those patches are absolutely unrelated to those
> failures.
>
> Please check into those issues - Thanks
It happened again
http:/
Looks like loop device issues.
Nir - didn't you say you have a patch to fix this?
In any case i think rebooting the slave fix this.
E.
On Wed, Jan 13, 2016 at 3:08 PM, Vinzenz Feenstra
wrote:
>
> On Jan 13, 2016, at 1:20 PM, Vinzenz Feenstra wrote:
>
> I have just submitted a set of 4 patches
Hi
Currently DB upgrade jobs are using schema.sh script and not engine-setup
This may cause CI upgrade tests to be successful while they are actually failed
when running from engine-setup
Since we are using engine-setup to upgrade the database, CI tests must use the
same exact method in order to
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/1655/
Build Number: 1655
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51628
Hi,
The scripts used to run the job can be found here [1].
Specifically:
ovirt-engine_upgrade-db.cleanup.sh
ovirt-engine_upgrade-db.sh
If you can submit a patch to replace the logic to use engine-setup instead,
the jobs will update automatically via yaml to use the new logic.
infra team can help
Also replacing support-infra with infra-support which is the right email to
open a ticket.
e.
On Wed, Jan 13, 2016 at 4:49 PM, Eyal Edri wrote:
> Hi,
>
> The scripts used to run the job can be found here [1].
> Specifically:
>
> ovirt-engine_upgrade-db.cleanup.sh
> ovirt-engine_upgrade-db.sh
>
I wonder if the upgrade jobs could somehow be converted into standard-CI.
Are they running on every merge atm?
On 13 January 2016 at 16:52, Eyal Edri wrote:
> Also replacing support-infra with infra-support which is the right email to
> open a ticket.
>
> e.
>
> On Wed, Jan 13, 2016 at 4:49 PM, E
Hi
Currently DB upgrade jobs are using schema.sh script and not engine-setup
This may cause CI upgrade tests to be successful while they are actually
failed when running from engine-setup
Since we are using engine-setup to upgrade the database, CI tests must use
the same exact method in or
Project:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/773/
Build Number: 773
Build Status: Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51747
--
Hi,
This is my key.
Please grant me access to resource.ovirt.org server.
Thanks in advance,
Lev Veyde.
lveyde.pub
Description: Binary data
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
On Wed, Jan 13, 2016 at 5:00 PM, Lev Veyde wrote:
> Hi,
>
> This is my key.
>
> Please grant me access to resource.ovirt.org server.
>
+1
>
> Thanks in advance,
> Lev Veyde.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at
VM Pools are a nice feature of oVirt.
A VM pool lets you quickly create a pool of stateles VMs all based on
the same template.
A VM pool also seems to currently be the only way to create
template-based thin QCOW2 VMs in oVirt. (Cloning from template creates
a thick copy, this is why its relatively
>>
>> Please grant me access to resource.ovirt.org server.
>
Dear integration team,
Please send patches like this: https://gerrit.ovirt.org/#/c/51673/1
instead of emails (But check it out and base on it as it creates the
file you need to add to).
This will streamline the process of you getting the
On Wed, Jan 13, 2016 at 5:42 PM, Barak Korren wrote:
> >>
> >> Please grant me access to resource.ovirt.org server.
> >
> Dear integration team,
> Please send patches like this: https://gerrit.ovirt.org/#/c/51673/1
I have no rights to see that patch.
>
> instead of emails (But check it out a
On Wed, Jan 13, 2016 at 5:47 PM, Sandro Bonazzola
wrote:
>
>
> On Wed, Jan 13, 2016 at 5:42 PM, Barak Korren wrote:
>
>> >>
>> >> Please grant me access to resource.ovirt.org server.
>> >
>> Dear integration team,
>> Please send patches like this: https://gerrit.ovirt.org/#/c/51673/1
>
>
> I hav
On 01/13 18:23, Barak Korren wrote:
> VM Pools are a nice feature of oVirt.
> A VM pool lets you quickly create a pool of stateles VMs all based on
> the same template.
> A VM pool also seems to currently be the only way to create
> template-based thin QCOW2 VMs in oVirt. (Cloning from template cre
hmm... right this is the 'secret' repo... never mind then, keep
emailing... unless david says otherwise...
On 13 January 2016 at 18:49, Sandro Bonazzola wrote:
>
>
> On Wed, Jan 13, 2016 at 5:47 PM, Sandro Bonazzola
> wrote:
>>
>>
>>
>> On Wed, Jan 13, 2016 at 5:42 PM, Barak Korren wrote:
>>>
On 01/13 18:53, Barak Korren wrote:
> hmm... right this is the 'secret' repo... never mind then, keep
> emailing... unless david says otherwise...
>
I think sandro is a good candidate to also send patches to that repo :)
>
> On 13 January 2016 at 18:49, Sandro Bonazzola wrote:
> >
> >
> > On
Hello All.
> What this comes down to is that if you run 'shutdown' in a VM from a
> > pool, you will automatically get back a clean VM a few minutes later.
> >
>
> Is there an easy way to do so from jenknis job without failing the job
> with slave connection error? Most projects I know that use ep
On 01/13 18:02, Anton Marchukov wrote:
> Hello All.
>
> > What this comes down to is that if you run 'shutdown' in a VM from a
> > > pool, you will automatically get back a clean VM a few minutes later.
> > >
> >
> > Is there an easy way to do so from jenknis job without failing the job
> > with s
On 01/13 15:37, Eyal Edri wrote:
> Looks like loop device issues.
> Nir - didn't you say you have a patch to fix this?
>
> In any case i think rebooting the slave fix this.
I just logged in to the slave and I see some strange loop devices that
don't look right:
[dcaro@fc21-vm09 ~]$ losetup
NAME
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/1660/
Build Number: 1660
Build Status: Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51720
--
Project:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/790/
Build Number: 790
Build Status: Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51417
--
Project:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/778/
Build Number: 778
Build Status: Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51419
--
Project:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/779/
Build Number: 779
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51715
Project:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/780/
Build Number: 780
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51639
On Wed, Jan 13, 2016 at 3:37 PM, Eyal Edri wrote:
> Looks like loop device issues.
> Nir - didn't you say you have a patch to fix this?
The patch was merge today:
https://gerrit.ovirt.org/51614/
It fixes incorrect umount in two tests, that may cause stale loop
devices effecting
other tests on sa
Project:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.6_el6_merged/781/
Build Number: 781
Build Status: Still Failing
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51801
Project:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_3.6_upgrade-from-3.5_el6_merged/796/
Build Number: 796
Build Status: Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51801
--
all errors in the console log aren't related to Alexander's
patch as implied by the original jenkins e-mail (forwarded
below):
...
ERROR with rpm_check_debug vs depsolve:
ovirt-engine-sdk-python >= 3.5.2.1 is needed by (installed)
ovirt-iso-uploader-3.5.2-1.el6.noarch
ovirt-engine-sdk-python >
Project:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/
Build:
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merged/1667/
Build Number: 1667
Build Status: Failure
Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/51257
--
On Wed, Jan 13, 2016 at 7:57 PM, David Caro wrote:
> On 01/13 15:37, Eyal Edri wrote:
>> Looks like loop device issues.
>> Nir - didn't you say you have a patch to fix this?
>>
>> In any case i think rebooting the slave fix this.
>
> I just logged in to the slave and I see some strange loop device
48 matches
Mail list logo
