[CQ]: 88501, 3 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause

2018-03-05 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 88501,3 (ovirt-engine-metrics) failed. However, this change seems not to be the root cause for this failure. Change 88250,4 (ovirt-engine-metrics) that this change depends on or is based on, was detected as the cause of the

Fwd: Still Failing: oVirt/ovirt-engine#4888 (master - 1cc377f)

2018-03-05 Thread Sandro Bonazzola
Hi, not sure who's monitoring Travis failures and maintaining Travis jobs, but looks like we have an error in the test suite It's currently failing on: --- T E S T S --- Running

[JIRA] (OVIRT-1861) Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available

2018-03-05 Thread sbonazzo (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sbonazzo updated OVIRT-1861: Component/s: wiki (MediaWiki) > Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available >

[JIRA] (OVIRT-1861) Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available

2018-03-05 Thread sbonazzo (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sbonazzo updated OVIRT-1861: Issue Type: Bug (was: By-EMAIL) > Re: [ovirt-users] [ANN] oVirt 4.1.9 Release is now available >

[JIRA] (OVIRT-1886) Add fcraw support for s390x and ppc64le

2018-03-05 Thread sbonazzo (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sbonazzo updated OVIRT-1886: Component/s: mock_runner CI Mirrors > Add fcraw support for s390x and ppc64le >

[JIRA] (OVIRT-1886) Add fcraw support for s390x and ppc64le

2018-03-05 Thread sbonazzo (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sbonazzo updated OVIRT-1886: Issue Type: New Feature (was: By-EMAIL) > Add fcraw support for s390x and ppc64le >

[CQ]: 88487, 5 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause

2018-03-05 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 88487,5 (ovirt-engine-metrics) failed. However, this change seems not to be the root cause for this failure. Change 88250,4 (ovirt-engine-metrics) that this change depends on or is based on, was detected as the cause of the

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 211 - Failure!

2018-03-05 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/211/ Build Number: 211 Build Status: Failure Triggered By: Started by timer - Changes Since Last

[CQ]: 88480, 2 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause

2018-03-05 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 88480,2 (ovirt-engine-metrics) failed. However, this change seems not to be the root cause for this failure. Change 88250,4 (ovirt-engine-metrics) that this change depends on or is based on, was detected as the cause of the

[oVirt Jenkins] ovirt-appliance_ovirt-4.2-snapshot_build-artifacts-el7-x86_64 - Build # 186 - Still Failing!

2018-03-05 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-snapshot_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2-snapshot_build-artifacts-el7-x86_64/186/ Build Number: 186 Build Status: Still Failing Triggered By: Started by timer

[oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 6 - Still Failing!

2018-03-05 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/6/ Build Number: 6 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last Success:

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-master - Build # 58 - Failure!

2018-03-05 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-master/58/ Build Number: 58 Build Status: Failure Triggered By: Started by timer - Changes

[CQ]: 87990, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

2018-03-05 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 87990,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88402,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 88459, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

2018-03-05 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 88459,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88402,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 88504,1 (ovirt-engine-metrics) failed "ovirt-4.2" system tests

2018-03-05 Thread oVirt Jenkins
Change 88504,1 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-4.2" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details

[CQ]: 88038, 6 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

2018-03-05 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 88038,6 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88402,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[CQ]: 88470, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

2018-03-05 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 88470,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88402,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

Re: [ovirt-devel] hosted-engine ovirt-system-tests

2018-03-05 Thread Yaniv Kaul
On Mon, Mar 5, 2018 at 3:01 PM, Yedidyah Bar David wrote: > Hi all, > > Recently I have been pushing various patches to OST in order to verify > specific bugs/fixes I was working on, using them with the "manual" > jenkins job but with no immediate intention to get them merged.

Re: [oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 5 - Still Failing!

2018-03-05 Thread Leon Goldberg
The API has been backported for a while. Engine patch[1] was backported/reviewed, should be merged shortly [1] https://gerrit.ovirt.org/#/c/88474/ On Mon, Mar 5, 2018 at 4:57 PM, Dan Kenigsberg wrote: > http://jenkins.ovirt.org/job/ovirt-system-tests_network- >

[JIRA] (OVIRT-1916) ovirt site doesn't render/publish the latest blog post

2018-03-05 Thread eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1916?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35967#comment-35967 ] eyal edri commented on OVIRT-1916: -- Can you please check? On Mon, Mar 5, 2018 at 4:25 PM, Roy Golan (oVirt

Re: [JIRA] (OVIRT-1916) ovirt site doesn't render/publish the latest blog post

2018-03-05 Thread Eyal Edri
Can you please check? On Mon, Mar 5, 2018 at 4:25 PM, Roy Golan (oVirt JIRA) < j...@ovirt-jira.atlassian.net> wrote: > Roy Golan created OVIRT-1916: > >Summary: ovirt site doesn't render/publish the latest blog post >Key: OVIRT-1916 >URL:

Re: [oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 5 - Still Failing!

2018-03-05 Thread Dan Kenigsberg
http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/5/console Leon, have you noticed that your new test for syncallnetworks runs on 4.2, too, while the API is introduced only on 4.3? Either backport the new API, or (more reasonably) avoid this test in 4.2. On Mon, Mar 5, 2018 at

[JIRA] (OVIRT-1916) ovirt site doesn't render/publish the latest blog post

2018-03-05 Thread Roy Golan (oVirt JIRA)
Roy Golan created OVIRT-1916: Summary: ovirt site doesn't render/publish the latest blog post Key: OVIRT-1916 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1916 Project: oVirt - virtualization made

Re: hosted-engine ovirt-system-tests

2018-03-05 Thread Yedidyah Bar David
On Mon, Mar 5, 2018 at 3:10 PM, Sandro Bonazzola wrote: > > > Il 5 mar 2018 2:02 PM, "Yedidyah Bar David" ha scritto: > > Hi all, > > Recently I have been pushing various patches to OST in order to verify > specific bugs/fixes I was working on, using them

[CQ]: 88438, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

2018-03-05 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 88438,3 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88402,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

Re: hosted-engine ovirt-system-tests

2018-03-05 Thread Sandro Bonazzola
Il 5 mar 2018 2:02 PM, "Yedidyah Bar David" ha scritto: Hi all, Recently I have been pushing various patches to OST in order to verify specific bugs/fixes I was working on, using them with the "manual" jenkins job but with no immediate intention to get them merged. Main reason

[ OST Failure Report ] [ oVirt 4.2 (ovirt-engine) ] [ 05-03-2018 ] [ 006_migrations.migrate_vm ]

2018-03-05 Thread Dafna Ron
Hi, We have a failure in OST on test 006_migrations.migrate_vm. >From what I can see, the migration succeeded but because there was a KeyError: 'cpuUsage' engine assume the v is down and tries to retry migration. the re-try fails with vm already exists. *Link and headline of suspected patches:

hosted-engine ovirt-system-tests

2018-03-05 Thread Yedidyah Bar David
Hi all, Recently I have been pushing various patches to OST in order to verify specific bugs/fixes I was working on, using them with the "manual" jenkins job but with no immediate intention to get them merged. Main reason is that it's not clear what's the best approach to get such tests merged.

[CQ]: 88323, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

2018-03-05 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 88323,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88402,4 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing

[oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 5 - Still Failing!

2018-03-05 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-4.2/5/ Build Number: 5 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last Success:

[CQ]: 88432, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-03-05 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 88432,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 88404,3 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures.