[JIRA] (OVIRT-1869) add new disk to templates.ovirt.org

2018-01-31 Thread Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Evgheni Dereveanchin reassigned OVIRT-1869: --- Assignee: Evgheni Dereveanchin (was: infra) > add new disk to

[JIRA] (OVIRT-1869) add new disk to templates.ovirt.org

2018-01-31 Thread Evgheni Dereveanchin (oVirt JIRA)
Evgheni Dereveanchin created OVIRT-1869: --- Summary: add new disk to templates.ovirt.org Key: OVIRT-1869 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1869 Project: oVirt - virtualization

[JIRA] (OVIRT-1712) OST jobs fails on "address already in use"

2018-01-31 Thread eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35724#comment-35724 ] eyal edri commented on OVIRT-1712: -- [~dbele...@redhat.com][~gbenh...@redhat.com] what was the latest fix on

[CQ]: 86912,2 (ovirt-engine) failed "ovirt-master" system tests

2018-01-31 Thread oVirt Jenkins
Change 86912,2 (ovirt-engine) 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 details

[oVirt Jenkins] ovirt-appliance_master_build-artifacts-el7-x86_64 - Build # 691 - Failure!

2018-01-31 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86_64/691/ Build Number: 691 Build Status: Failure Triggered By: Started by timer -

[JIRA] (OVIRT-1712) OST jobs fails on "address already in use"

2018-01-31 Thread eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35726#comment-35726 ] eyal edri commented on OVIRT-1712: -- So what is the alternate fix? > OST jobs fails on "address already in

[CQ]: 86944,1 (ioprocess) failed "ovirt-master" system tests

2018-01-31 Thread oVirt Jenkins
Change 86944,1 (ioprocess) 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 details about

[JIRA] (OVIRT-1712) OST jobs fails on "address already in use"

2018-01-31 Thread Dafna Ron (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35722#comment-35722 ] Dafna Ron commented on OVIRT-1712: -- We had 2 failures today on network in use. in the latest one I can see

[JIRA] (OVIRT-1712) OST jobs fails on "address already in use"

2018-01-31 Thread Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35725#comment-35725 ] Daniel Belenky commented on OVIRT-1712: --- We've abandoned the fix from mock_runner's side for now > OST

[CQ]: 86940, 3 (ovirt-setup-lib) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-01-31 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 86940,3 (ovirt-setup-lib) failed. However, this change seems not to be the root cause for this failure. Change 86938,2 (ovirt-setup-lib) that this change depends on or is based on, was detected as the cause of the testing

Jenkins build is back to normal : system-sync_mirrors-centos-updates-el7-x86_64 #1230

2018-01-31 Thread jenkins
See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

[CQ]: 83154,4 (ovirt-engine-wildfly) failed "ovirt-4.2" system tests

2018-01-31 Thread oVirt Jenkins
Change 83154,4 (ovirt-engine-wildfly) 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

[JIRA] (OVIRT-1870) kubevirt_kubevirt_standard-check-pr jobs often get stuck

2018-01-31 Thread Evgheni Dereveanchin (oVirt JIRA)
Evgheni Dereveanchin created OVIRT-1870: --- Summary: kubevirt_kubevirt_standard-check-pr jobs often get stuck Key: OVIRT-1870 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1870 Project: oVirt

[JIRA] (OST-99) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium

2018-01-31 Thread eyal edri (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OST-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri moved OVIRT-1788 to OST-99: - Component/s: (was: OST) Project: oVirt system tests (was: oVirt -

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1229

2018-01-31 Thread jenkins
See Changes: [Dafna Ron] ovirt-host-deploy - dropping fc24 [Sandro Bonazzola] ovirt-host-deploy: re-align [Dafna Ron] ovirt-engine-wildfly - dropping fc24 [Sandro Bonazzola]

oVirt infra weekly meeting notes 31.01.2018

2018-01-31 Thread Evgheni Dereveanchin
Hi everyone, Please find the topics of this week's infra meeting below: PHX DC - Core network equipment change completed on Monday - Repo definitions removed from puppet as part of OVIRT-1810 - New Fedora 27 snapshot

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

2018-01-31 Thread jenkins
Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64/421/ Build Number: 421 Build Status: Still Failing Triggered By: Started by timer

[JIRA] (OVIRT-1870) kubevirt_kubevirt_standard-check-pr jobs often get stuck

2018-01-31 Thread Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren reassigned OVIRT-1870: --- Assignee: Barak Korren (was: infra) Component/s: Standard CI (Pipelines)

[JIRA] (OVIRT-1870) kubevirt_kubevirt_standard-check-pr jobs often get stuck

2018-01-31 Thread Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1870: Epic Link: OVIRT-400 > kubevirt_kubevirt_standard-check-pr jobs often get stuck >

[JIRA] (OVIRT-1712) OST jobs fails on "address already in use"

2018-01-31 Thread Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=35730#comment-35730 ] Daniel Belenky commented on OVIRT-1712: --- [~eedri] We'll probably add a cleanup function to global setup

[CQ]: 86950, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-01-31 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 86950,1 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 86692,1 (ovirt-engine-api-model) that this change depends on or is based on, was detected as the cause of the

[CQ]: 86951, 1 (ovirt-engine-api-model) failed "ovirt-4.2" system tests, but isn't the failure root cause

2018-01-31 Thread oVirt Jenkins
A system test invoked by the "ovirt-4.2" change queue including change 86951,1 (ovirt-engine-api-model) failed. However, this change seems not to be the root cause for this failure. Change 86692,1 (ovirt-engine-api-model) that this change depends on or is based on, was detected as the cause of the

[CQ]: 85206,1 (ovirt-iso-uploader) failed "ovirt-4.2" system tests

2018-01-31 Thread oVirt Jenkins
Change 85206,1 (ovirt-iso-uploader) 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