Jenkins build is still unstable: ovirt_master_publish-rpms_nightly #753

See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build became unstable: ovirt_4.1_publish-rpms_nightly #361

See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #9

See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

Jenkins build is back to normal : system-sync_mirrors-epel-el6-x86_64 #873

See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

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

See ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

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

See -- Started by upstream project "ovirt-release_master_build-artifacts-el7-x86_64" build number 557 originally caused by: Started by timer [EnvInject] - Loading node

Re: Planned restart of production services

Maintenance completed, services are back up and running. Please re-trigger builds if you submitted patches while Jenkins was offline. As always - if you see any issues please report them to Jira. Regards, Evgheni Dereveanchin On Wed, Nov 1, 2017 at 11:44 PM, Evgheni Dereveanchin

oVirt infra daily report - unstable production jobs - 492

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/492//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

Planned restart of production services

Hi everyone, I'll be restarting several production systems today to perform planned maintenance. The following services may be unreachable for some period of time: - resources.ovirt.org - software repositories - jenkins.ovirt.org - CI master No new builds will be started during this period. I

[CQ]: 83487, 1 (imgbased) failed "ovirt-4.1" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.1" change queue including change 83487,1 (imgbased) failed. However, this change seems not to be the root cause for this failure. Change 83420,1 (imgbased) that this change depends on or is based on, was detected as the cause of the testing failures. This

[CQ]: 83420,1 (imgbased) failed "ovirt-4.1" system tests

Change 83420,1 (imgbased) is probably the reason behind recent system test failures in the "ovirt-4.1" 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 the

oVirt infra weekly meeting notes 01.11.2017

Hi everyone, please find the topics of today's infra meeting below: - Staging Engine still has Gluster issues OVIRT-1121 - Ticket created to automate staging Engine auto-updates to Master OVIRT-1729

[CQ]: 82822, 4 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-master" change queue including change 82822,4 (ovirt-hosted-engine-ha) failed. However, this change seems not to be the root cause for this failure. Change 83278,1 (ovirt-hosted-engine-ha) that this change depends on or is based on, was detected as the cause of

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

A system test invoked by the "ovirt-master" change queue including change 82823,6 (ovirt-hosted-engine-ha) failed. However, this change seems not to be the root cause for this failure. Change 83278,1 (ovirt-hosted-engine-ha) that this change depends on or is based on, was detected as the cause of

[CQ]: 83487, 1 (imgbased) failed "ovirt-4.1" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.1" change queue including change 83487,1 (imgbased) failed. However, this change seems not to be the root cause for this failure. Change 83420,1 (imgbased) that this change depends on or is based on, was detected as the cause of the testing failures. This

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #872

See Changes: [Gil Shinar] Change the commit message order in poll us scripts [Gal Ben Haim] lago: Drop fc24 build for lago and lago-ovirt [Gal Ben Haim] lago: Add fc27 build for lago and

[JIRA] (OVIRT-1474) automerge poll stage patches

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1474: Labels: poll-upstream-sources standard-ci (was: standard-ci) > automerge poll stage patches >

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barak Korren updated OVIRT-1732: Epic Link: OVIRT-400 > Make 'poll-upstream-chages' job abandon old changes it made >

[JIRA] (OVIRT-1732) Make 'poll-upstream-chages' job abandon old changes it made

Barak Korren created OVIRT-1732: --- Summary: Make 'poll-upstream-chages' job abandon old changes it made Key: OVIRT-1732 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1732 Project: oVirt -

[ OST Failure Report ] [ oVirt 4.1 ] [ Nov 1st 2017 ] [002_bootstrap.add_dc, 002_bootstrap.add_master_storage_domain ]

Hi, we have failures in 4.1 imagebased. I think it's also related to the same package from 4.2 that is downloaded in the 4.1 repo. 2017-11-01 13:17:53,817::ssh.py::ssh::96::lago.ssh::DEBUG::Command 10946280 on lago-basic-suite-4-1-host-0 errors: Error: Package:

[ OST Failure Report ] [ oVirt 4.1 ] [ Nov 1st 2017 ] [ 002_bootstrap.add_master_storage_domain]

Hi, There are three reported failures on the same test: 002_bootstrap.add_master_storage_domain This seems to be related to packages issues. Please note that all 3 suits failed. Basic suit failed because of ovirt-host-4.2.0-0.0 and i think all related issues came from there. upgrade suits

[JIRA] (OVIRT-1731) Add storage monitoring to templates.ovirt.org

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gal Ben Haim reassigned OVIRT-1731: --- Assignee: Evgheni Dereveanchin (was: infra) > Add storage monitoring to

[JIRA] (OVIRT-1731) Add storage monitoring to templates.ovirt.org

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gal Ben Haim updated OVIRT-1731: Issue Type: New Feature (was: Bug) > Add storage monitoring to templates.ovirt.org >

[JIRA] (OVIRT-1731) Add storage monitoring to templates.ovirt.org

Gal Ben Haim created OVIRT-1731: --- Summary: Add storage monitoring to templates.ovirt.org Key: OVIRT-1731 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1731 Project: oVirt - virtualization made easy

[CQ]: 83487, 1 (imgbased) failed "ovirt-4.1" system tests, but isn't the failure root cause

A system test invoked by the "ovirt-4.1" change queue including change 83487,1 (imgbased) failed. However, this change seems not to be the root cause for this failure. Change 83420,1 (imgbased) that this change depends on or is based on, was detected as the cause of the testing failures. This

Re: [JIRA] (OVIRT-1730) Jenkins job http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/18737/ is stuck for an hour.

Here is another job experiencing the same: http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/18745 On Wed, Nov 1, 2017 at 11:47 AM, Edward Haas (oVirt JIRA) < j...@ovirt-jira.atlassian.net> wrote: > Edward Haas created OVIRT-1730: > >Summary: Jenkins job >

[CQ]: 83420,1 (imgbased) failed "ovirt-4.1" system tests

Change 83420,1 (imgbased) is probably the reason behind recent system test failures in the "ovirt-4.1" 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 the

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt master ] [ 01 Nov 2017 ] [ 098_ovirt_provider_ovn.test_ovn_provider_rest ]

Adding Marcin. On Wed, Nov 1, 2017 at 12:01 PM, Dafna Ron wrote: > Hi, > > 098_ovirt_provider_ovn.test_ovn_provider_rest failed on removing the > interface from a running vm. > > I have seen this before, do we perhaps have a race in OST where the vm is > still running at times?

[JIRA] (OVIRT-1730) Jenkins job http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/18737/ is stuck for an hour.

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri reassigned OVIRT-1730: Assignee: Evgheni Dereveanchin (was: infra) > Jenkins job >

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

A system test invoked by the "ovirt-4.1" change queue including change 83394,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 83403,1 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures.

[ OST Failure Report ] [ oVirt master ] [ 01 Nov 2017 ] [ 098_ovirt_provider_ovn.test_ovn_provider_rest ]

Hi, 098_ovirt_provider_ovn.test_ovn_provider_rest failed on removing the interface from a running vm. I have seen this before, do we perhaps have a race in OST where the vm is still running at times? ** *Link to suspected patches: Patch reported is below but I am suspecting its a race and not

[JIRA] (OVIRT-1730) Jenkins job http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/18737/ is stuck for an hour.

Edward Haas created OVIRT-1730: -- Summary: Jenkins job http://jenkins.ovirt.org/job/vdsm_master_check-patch-el7-x86_64/18737/ is stuck for an hour. Key: OVIRT-1730 URL:

Change in barak-test[master]: Another test change

>From Barak Korren : Barak Korren has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/12 ) Change subject: Another test change .. Patch Set 1: testing jenkins trigger on post-merge

[oVirt Jenkins] standard-enqueue - Build #6283 - FAILURE!

Build: http://jenkins.ovirt.org/job/standard-enqueue/6283/ Build Name: #6283 Build Description: Gerrit: 82686 - ovirt-host-deploy (master) Build Status: FAILURE Gerrit change: null - title: null - project: ovirt-host-deploy - branch: null - author: null

Re: [ovirt-devel] [ OST Failure Report ] [ oVirt 4.1] [ 31 Oct 2017 ] [ 002_bootstrap.add_dc ]

I think you need to change the external bash call from `bash -s` to `bash -se` On Tue, Oct 31, 2017 at 10:03 PM, Barak Korren wrote: > > > On 31 October 2017 at 17:56, Gal Ben Haim wrote: > >> The thing that bothers me is why the deploy script returned