[CQ]: 92289, 12 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause

2018-07-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 92289,12 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 92202,14 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 87 - Fixed!

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/87/ Build Number: 87 Build Status: Fixed Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 313 - Fixed!

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/313/ Build Number: 313 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success:

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-4.2 - Build # 337 - Fixed!

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/337/ Build Number: 337 Build Status: Fixed Triggered By: Started by timer - Changes Since

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 353 - Still Failing!

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/353/ Build Number: 353 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 532 - Fixed!

2018-07-01 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/532/ Build Number: 532 Build Status: Fixed Triggered By: Started by timer - Changes Since Last

[CQ]: 92363, 10 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause

2018-07-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 92363,10 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 92202,14 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 565 - Fixed!

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/565/ Build Number: 565 Build Status: Fixed Triggered By: Started by timer - Changes Since Last

[oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 352 - Fixed!

2018-07-01 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/352/ Build Number: 352 Build Status: Fixed Triggered By: Started by timer - Changes Since Last Success:

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 86 - Still Failing!

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/86/ Build Number: 86 Build Status: Still Failing Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 295 - Fixed!

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/295/ Build Number: 295 Build Status: Fixed Triggered By: Started by timer - Changes

[CQ]: 92202, 14 (ovirt-provider-ovn) failed "ovirt-master" system tests

2018-07-01 Thread oVirt Jenkins
Change 92202,14 (ovirt-provider-ovn) is probably the reason behind recent system test failures in the "ovirt-master" 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

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 312 - Failure!

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/312/ Build Number: 312 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success:

[CQ]: 92590,7 (ovirt-engine) failed "ovirt-4.2" system tests

2018-07-01 Thread oVirt Jenkins
Change 92590,7 (ovirt-engine) 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 about

Re: [CQ]: 92610,3 (ovirt-engine) failed "ovirt-4.2" system tests

2018-07-01 Thread Barak Korren
On 1 July 2018 at 18:32, Daniel Belenky wrote: > Seems that the root cause is the fact that CQ tester is using stdci_runner > now and stdci_runner is not taking 'extra_sources' into account. > I guess I should've been more careful in the review, and you should be more careful refactoring! I

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 352 - Still Failing!

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/352/ Build Number: 352 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

Jenkins build is back to normal : deploy-to_ovirt-master_tested #4158

2018-07-01 Thread jenkins
See ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt

Re: [CQ]: 92610,3 (ovirt-engine) failed "ovirt-4.2" system tests

2018-07-01 Thread Daniel Belenky
Seems that the root cause is the fact that CQ tester is using stdci_runner now and stdci_runner is not taking 'extra_sources' into account. Meanwhile, I've reverted the change so we can re-examine stdci_runner.groovy https://gerrit.ovirt.org/#/c/92714/ On Sun, Jul 1, 2018 at 5:59 PM Daniel

Re: [CQ]: 92610,3 (ovirt-engine) failed "ovirt-4.2" system tests

2018-07-01 Thread Daniel Belenky
Hi, There's something that seems odd to me. @Barak Korren @Gal Ben Haim would appreciate you to have a look as well. According to Alona, the patch that introduced the error is: https://gerrit.ovirt.org/#/c/92009/ It was *tested* (and *deployed*) in

Re: Lack of resources on the ML server

2018-07-01 Thread Eyal Edri
Thanks for the update, Do we need a JIRA ticket to track this? On Tue, Jun 26, 2018 at 2:02 PM Marc Dequènes (Duck) wrote: > Quack, > > Sandro noticed some posts did not appear quickly on the interface. > There's quite a lot of traffic and it was not keeping up, so I added a > vCPU (2->3), but

Build failed in Jenkins: deploy-to_ovirt-master_tested #4157

2018-07-01 Thread jenkins
See -- Started by upstream project "ovirt-appliance_master_build-artifacts-el7-x86_64" build number 843 originally caused by: Started by timer [EnvInject] - Loading node

[JIRA] (OVIRT-2269) gerrit hooks checking for Bug-Url recognize Bug-Id as valid instead of failing

2018-07-01 Thread Eyal Edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri updated OVIRT-2269: - Component/s: Gerrit Hooks > gerrit hooks checking for Bug-Url recognize Bug-Id as valid instead of

[CQ]: 92612,3 (ovirt-engine) failed "ovirt-4.2" system tests

2018-07-01 Thread oVirt Jenkins
Change 92612,3 (ovirt-engine) 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 about

Re: [CQ]: 92610,3 (ovirt-engine) failed "ovirt-4.2" system tests

2018-07-01 Thread Eyal Edri
Please prepare an RCA how we hit again a bug in the script if it was verified before deployment. On Sun, Jul 1, 2018 at 4:40 PM Ehud Yonasi wrote: > Due to a bug in the retention policy, some packages were deleted from > tested repo. > We're rollbacking from nightly snapshot for all versions,

Re: [CQ]: 92610,3 (ovirt-engine) failed "ovirt-4.2" system tests

2018-07-01 Thread Daniel Belenky
Restore from master snapshot is done now. I've re-built https://jenkins.ovirt.org/job/ovirt-system-tests_manual/2878/ which should verify Alona's fix. Once things will clear out with this issue, I'll try to figure out how one 'bad' change affected all projects. On Sun, Jul 1, 2018 at 4:40 PM

Re: [CQ]: 92610,3 (ovirt-engine) failed "ovirt-4.2" system tests

2018-07-01 Thread Ehud Yonasi
Due to a bug in the retention policy, some packages were deleted from tested repo. We're rollbacking from nightly snapshot for all versions, and will update asap. On Sun, Jul 1, 2018 at 4:37 PM Ehud Yonasi wrote: > failed on installing packages. restoring tested repo > > > On Sun, Jul 1, 2018

Re: [CQ]: 92610,3 (ovirt-engine) failed "ovirt-4.2" system tests

2018-07-01 Thread Ehud Yonasi
failed on installing packages. restoring tested repo On Sun, Jul 1, 2018 at 4:34 PM Ehud Yonasi wrote: > will trigger the job again > > > On Sun, Jul 1, 2018 at 3:27 PM oVirt Jenkins wrote: > >> Change 92610,3 (ovirt-engine) is probably the reason behind recent system >> test >> failures in

Re: [CQ]: 92289, 12 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause

2018-07-01 Thread Ehud Yonasi
failed on installing packages. restoring tested repo On Sun, Jul 1, 2018 at 4:33 PM Ehud Yonasi wrote: > will trigger the job again > > > On Sun, Jul 1, 2018 at 3:45 PM oVirt Jenkins wrote: > >> A system test invoked by the "ovirt-master" change queue including change >> 92289,12

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 531 - Still Failing!

2018-07-01 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/531/ Build Number: 531 Build Status: Still Failing Triggered By: Started by timer - Changes Since

Re: [CQ]: 92610,3 (ovirt-engine) failed "ovirt-4.2" system tests

2018-07-01 Thread Ehud Yonasi
will trigger the job again On Sun, Jul 1, 2018 at 3:27 PM oVirt Jenkins wrote: > Change 92610,3 (ovirt-engine) 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

Re: [CQ]: 92289, 12 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause

2018-07-01 Thread Ehud Yonasi
will trigger the job again On Sun, Jul 1, 2018 at 3:45 PM oVirt Jenkins wrote: > A system test invoked by the "ovirt-master" change queue including change > 92289,12 (ovirt-provider-ovn) failed. However, this change seems not to be > the > root cause for this failure. Change 92202,14

Re: [ovirt-devel] Gerrit trying to set 3rd party cookies

2018-07-01 Thread Nir Soffer
On Sun, Jul 1, 2018 at 4:24 PM Barak Korren wrote: > On 1 July 2018 at 15:41, Nir Soffer wrote: > >> After watching Sarah Bird's great talk about the terrifying web[1], I >> found that for >> some reason 3rd party cookies were enabled in my browser. >> >> After disabling them, I found that

Re: [ovirt-devel] Gerrit trying to set 3rd party cookies

2018-07-01 Thread Barak Korren
On 1 July 2018 at 15:41, Nir Soffer wrote: > After watching Sarah Bird's great talk about the terrifying web[1], I > found that for > some reason 3rd party cookies were enabled in my browser. > > After disabling them, I found that gerrit is using 3rd party cookies from > gravatar.com. > (see

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

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/564/ Build Number: 564 Build Status: Failure Triggered By: Started by timer - Changes Since Last

[CQ]: 92289, 12 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause

2018-07-01 Thread oVirt Jenkins
A system test invoked by the "ovirt-master" change queue including change 92289,12 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 92202,14 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the

Gerrit trying to set 3rd party cookies

2018-07-01 Thread Nir Soffer
After watching Sarah Bird's great talk about the terrifying web[1], I found that for some reason 3rd party cookies were enabled in my browser. After disabling them, I found that gerrit is using 3rd party cookies from gravatar.com. (see attached screenshot). Why do we allow 3rd parties like

[CQ]: 92610,3 (ovirt-engine) failed "ovirt-4.2" system tests

2018-07-01 Thread oVirt Jenkins
Change 92610,3 (ovirt-engine) 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 about

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 294 - Failure!

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/294/ Build Number: 294 Build Status: Failure Triggered By: Started by timer - Changes

[oVirt Jenkins] ovirt-system-tests_network-suite-4.2 - Build # 351 - Failure!

2018-07-01 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/351/ Build Number: 351 Build Status: Failure Triggered By: Started by timer - Changes Since Last Success:

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 85 - Failure!

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/85/ Build Number: 85 Build Status: Failure Triggered By: Started by timer - Changes Since Last

[JIRA] (OVIRT-1878) GitHub support for pusher.py

2018-07-01 Thread Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37310#comment-37310 ] Barak Korren commented on OVIRT-1878: - [~eedri] probably a similar flow, but likely a different API. And

[JIRA] (OVIRT-1878) GitHub support for pusher.py

2018-07-01 Thread Eyal Edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37309#comment-37309 ] Eyal Edri commented on OVIRT-1878: -- We need to support GitLab as well, as that is the standard for downstream

[CQ]: 92202, 14 (ovirt-provider-ovn) failed "ovirt-master" system tests

2018-07-01 Thread oVirt Jenkins
Change 92202,14 (ovirt-provider-ovn) is probably the reason behind recent system test failures in the "ovirt-master" 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

Re: [ OST Failure Report ] [ oVirt Master (ovirt-engine) ] [ 28-06-2018 ] [ 098_ovirt_provider_ovn.use_ovn_provider.]

2018-07-01 Thread Ehud Yonasi
Hey Alona, what is the current status of the fix? On Thu, Jun 28, 2018 at 5:57 PM Dafna Ron wrote: > vdsm also failing on the same issue: > > https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8407/ > > Thanks, > Dafna > > > On Thu, Jun 28, 2018 at 11:11 AM, Dafna Ron wrote: > >>

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 351 - Still Failing!

2018-07-01 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/351/ Build Number: 351 Build Status: Still Failing Triggered By: Started by timer - Changes Since Last

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

2018-07-01 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/530/ Build Number: 530 Build Status: Failure Triggered By: Started by timer - Changes Since Last

[JIRA] (OVIRT-2265) ovirt-engine cq failing on test 098_ovirt_provider_ovn.use_ovn_provider - libvirtError: 'queues' attribute must be positive number:

2018-07-01 Thread Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=37307#comment-37307 ] Barak Korren commented on OVIRT-2265: - If you think https://gerrit.ovirt.org/#/c/92567/ is not the cause