- Infra - oVirt List Archives

[CQ]: 91568, 10 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

A system test invoked by the "ovirt-4.2" change queue including change 91568,10 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 91571,9 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91571,9 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91568/10 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91571/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2207/

1 0

[CQ]: 91599, 4 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

A system test invoked by the "ovirt-4.2" change queue including change 91599,4 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 91571,9 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91571,9 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91599/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91571/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2201/

1 0

[CQ]: 91588,2 (otopi) failed "ovirt-4.2" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 91588,2 (otopi) 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 the change see: https://gerrit.ovirt.org/#/c/91588/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2195/

1 0

[CQ]: 91611,1 (ovirt-host) failed "ovirt-4.2" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 91611,1 (ovirt-host) 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 the change see: https://gerrit.ovirt.org/#/c/91611/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2189/

1 0

[CQ]: 91571,9 (ovirt-provider-ovn) failed "ovirt-4.2" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 91571,9 (ovirt-provider-ovn) 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 the change see: https://gerrit.ovirt.org/#/c/91571/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2183/

1 0

[CQ]: 91568, 10 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

A system test invoked by the "ovirt-4.2" change queue including change 91568,10 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 91571,9 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91571,9 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91568/10 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91571/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2177/

1 0

[CQ]: 91599, 4 (ovirt-provider-ovn) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

A system test invoked by the "ovirt-4.2" change queue including change 91599,4 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 91571,9 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91571,9 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91599/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91571/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2170/

1 0

[CQ]: 91571,9 (ovirt-provider-ovn) failed "ovirt-4.2" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 91571,9 (ovirt-provider-ovn) 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 the change see: https://gerrit.ovirt.org/#/c/91571/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2163/

1 0

[CQ]: 91744,1 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 91744,1 (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 the change see: https://gerrit.ovirt.org/#/c/91744/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2155/

1 0

[CQ]: 91733, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

A system test invoked by the "ovirt-4.2" change queue including change 91733,1 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91638,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91638,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91733/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91638/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2149/

1 0

[JIRA] (OVIRT-2072) build-artifacts job failed to fetch git with returned status code 143
by Dafna Ron (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2072?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2072: ----------------------------- Labels: cq-issue-traking ost_failures ost_infra (was: ost_failures ost_infra) > build-artifacts job failed to fetch git with returned status code 143 > --------------------------------------------------------------------- > > Key: OVIRT-2072 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2072 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_failures, ost_infra > > put vm offline (could not see a host in log) and re-ran the artifacts job. > Change 91568,10 (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 details about the change see: > https://gerrit.ovirt.org/#/c/91568/10 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7993/ > 08:50:28 > git init /home/jenkins/workspace/ovirt-provider-ovn_master_build-artifacts-fc27-x86_64/ovirt-provider-ovn # timeout=10 > 08:50:28 Fetching upstream changes from git://gerrit.ovirt.org/ovirt-provider-ovn.git > 08:50:28 > git --version # timeout=10 > 08:50:28 > git fetch --tags --progress git://gerrit.ovirt.org/ovirt-provider-ovn.git +refs/heads/*:refs/remotes/origin/* > 09:00:28 ERROR: Timeout after 10 minutes > 09:00:28 ERROR: Error cloning remote repo 'origin' > 09:00:28 hudson.plugins.git.GitException: Command "git fetch --tags --progress git://gerrit.ovirt.org/ovirt-provider-ovn.git +refs/heads/*:refs/remotes/origin/*" returned status code 143: > 09:00:28 stdout: > 09:00:28 stderr: remote: Counting objects: 84340 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

post-merge CI triggering from GitHub
by Barak Korren 31 May '18

31 May '18

Its broken right now, we're investigating the issue. Tracker ticket: https://ovirt-jira.atlassian.net/browse/OVIRT-2071 Thanks Tomas Golembiovsky for reporting! -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 1

[CQ]: 91732, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

A system test invoked by the "ovirt-4.2" change queue including change 91732,1 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91638,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91638,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91732/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91638/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2142/

2 1

[CQ]: 72008, 1 (ovirt-engine-extension-aaa-misc) failed "ovirt-master" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 72008,1 (ovirt-engine-extension-aaa-misc) 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 the change see: https://gerrit.ovirt.org/#/c/72008/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7997/

1 0

[JIRA] (OVIRT-2072) build-artifacts job failed to fetch git with returned status code 143
by Dafna Ron (oVirt JIRA) 31 May '18

31 May '18

Dafna Ron created OVIRT-2072: -------------------------------- Summary: build-artifacts job failed to fetch git with returned status code 143 Key: OVIRT-2072 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2072 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra put vm offline (could not see a host in log) and re-ran the artifacts job. Change 91568,10 (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 details about the change see: https://gerrit.ovirt.org/#/c/91568/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7993/ 08:50:28 > git init /home/jenkins/workspace/ovirt-provider-ovn_master_build-artifacts-fc27-x86_64/ovirt-provider-ovn # timeout=10 08:50:28 Fetching upstream changes from git://gerrit.ovirt.org/ovirt-provider-ovn.git 08:50:28 > git --version # timeout=10 08:50:28 > git fetch --tags --progress git://gerrit.ovirt.org/ovirt-provider-ovn.git +refs/heads/*:refs/remotes/origin/* 09:00:28 ERROR: Timeout after 10 minutes 09:00:28 ERROR: Error cloning remote repo 'origin' 09:00:28 hudson.plugins.git.GitException: Command "git fetch --tags --progress git://gerrit.ovirt.org/ovirt-provider-ovn.git +refs/heads/*:refs/remotes/origin/*" returned status code 143: 09:00:28 stdout: 09:00:28 stderr: remote: Counting objects: 84340 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 91568, 10 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 91568,10 (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 details about the change see: https://gerrit.ovirt.org/#/c/91568/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7993/

1 0

[JIRA] (OVIRT-2071) post-merge triggering from GitHub Isn't working (again)
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2071?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2071: ----------------------------------- Assignee: Barak Korren (was: infra) > post-merge triggering from GitHub Isn't working (again) > ------------------------------------------------------- > > Key: OVIRT-2071 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2071 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: GitHub, Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: Barak Korren > > Post merge events fro github are triggering (via webhooks) the 'standard-webhook-trigger' job but for some reason jenkins is no longer passing the information from the GitHub webhook to it , so the job cannot trigger the proper STDCI job to handle the merge event. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2071) post-merge triggering from GitHub Isn't working (again)
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

Barak Korren created OVIRT-2071: ----------------------------------- Summary: post-merge triggering from GitHub Isn't working (again) Key: OVIRT-2071 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2071 Project: oVirt - virtualization made easy Issue Type: Outage Components: GitHub, Standard CI (Pipelines) Reporter: Barak Korren Assignee: infra Post merge events fro github are triggering (via webhooks) the 'standard-webhook-trigger' job but for some reason jenkins is no longer passing the information from the GitHub webhook to it , so the job cannot trigger the proper STDCI job to handle the merge event. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2071) post-merge triggering from GitHub Isn't working (again)
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2071?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2071: -------------------------------- Epic Link: OVIRT-400 > post-merge triggering from GitHub Isn't working (again) > ------------------------------------------------------- > > Key: OVIRT-2071 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2071 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: GitHub, Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: infra > > Post merge events fro github are triggering (via webhooks) the 'standard-webhook-trigger' job but for some reason jenkins is no longer passing the information from the GitHub webhook to it , so the job cannot trigger the proper STDCI job to handle the merge event. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2070) Please add Martin Necas to oVirt organization on github
by eyal edri (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2070?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2070: ----------------------------- Assignee: eyal edri (was: infra) Resolution: Fixed Status: Done (was: To Do) Added. > Please add Martin Necas to oVirt organization on github > ------------------------------------------------------- > > Key: OVIRT-2070 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2070 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Martin Perina > Assignee: eyal edri > > Hi, > could you please add Martin Necas (alias ocasek) to oVirt organization on github? > Thanks > Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2055) failure in suspend resume vm not related to reported change - need to investigate
by Dafna Ron (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2055?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2055: ---------------------------------- as this is random, we need to see if resume suspend vm is still failing periodically and if so if we see the same errors, > failure in suspend resume vm not related to reported change - need to investigate > --------------------------------------------------------------------------------- > > Key: OVIRT-2055 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2055 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > Change 91507,1 (ovirt-engine-sdk-java) 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 the change see: > https://gerrit.ovirt.org/#/c/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > I think the issue is on qemu/libvirt changed queries: > https://pastebin.com/afyeUAcT > https://pastebin.com/va20Y5Hp > checking his with vdsm people. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2054) false change reported since package is not deployed on ost
by Dafna Ron (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2054?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2054: ---------------------------------- Barak, any advice on how to start investigating this? > false change reported since package is not deployed on ost > ---------------------------------------------------------- > > Key: OVIRT-2054 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > Change 91507,1 (ovirt-engine-sdk-java) 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 the change see: > https://gerrit.ovirt.org/#/c/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > The package is not deployed on OST so it could not have been the reason for failure. > + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report. > Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2056) All CQ failing due to ovirt-4.1 centos being EOL
by Dafna Ron (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2056?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2056: ----------------------------- Resolution: Fixed Status: Done (was: To Do) patch solved the issue. closing > All CQ failing due to ovirt-4.1 centos being EOL > ------------------------------------------------ > > Key: OVIRT-2056 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2056 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > 21:50:07 [upgrade-from-release-suit] raise e > 21:50:07 [upgrade-from-release-suit] yum.Errors.NoMoreMirrorsRepoError: failure: repodata/repomd.xml from centos-ovirt-4.1-el7: [Errno 256] No more mirrors to try. > 21:50:07 [upgrade-from-release-suit] http://mirror.centos.org/centos/7.4.1708/virt/x86_64/ovirt-4.1/repodata/rep…: [Errno 14] HTTP Error 404 - Not Found > 21:50:07 [upgrade-from-release-suit] > 21:50:07 [upgrade-from-release-suit] * Running reposync: ERROR (in 0:00:01) > 21:50:07 [upgrade-from-release-suit] # Syncing remote repos locally (this might take some time): ERROR (in 0:00:01) > 21:50:07 [upgrade-from-release-suit] @ Create prefix internal repo: ERROR (in 0:00:01) > 21:50:07 [upgrade-from-release-suit] Error occured, aborting -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2046) Bring up Trello-Bugzilla automation inside OpenShift to support oVirt 4.3 agile flow
by Evgheni Dereveanchin (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2046?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2046: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Bring up Trello-Bugzilla automation inside OpenShift to support oVirt 4.3 agile flow > ------------------------------------------------------------------------------------ > > Key: OVIRT-2046 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2046 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: Evgheni Dereveanchin > Priority: High > > Please bring up a service on shift.ovirt.org to support multiple Trello board for the oVirt team to integrate with Bugzilla. > [~msivak(a)redhat.com] should have all the relevant info the deployment, which works well locally on containers. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[oVirt Jenkins] ovirt-node-ng_4.2_build-artifacts-el7-x86_64 - Build # 89 - Failure!
by jenkins＠jenkins.phx.ovirt.org 31 May '18

31 May '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/ Build: http://jenkins.ovirt.org/job/ovirt-node-ng_4.2_build-artifacts-el7-x86_64/8… Build Number: 89 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #89 [Daniel Belenky] Introduce STDCI summary [Sandro Bonazzola] ovirt-image-uploader: drop 4.1 jobs, move to fc28 [Sandro Bonazzola] ovirt-setup-lib: drop 4.1, move to fc28 [Daniel Belenky] Fix a typo in standard-stage analizer->analyzer [gzaidman] ovirt-engine: move from fc27 to fc28 [Sandro Bonazzola] kickstart: drop upstream cockpit copr repo ----------------- Failed Tests: ----------------- No tests ran.

1 1

[CQ]: 91731, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

A system test invoked by the "ovirt-4.2" change queue including change 91731,1 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91638,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91638,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91731/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91638/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2135/

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 187 - Failure!
by jenkins＠jenkins.phx.ovirt.org 31 May '18

31 May '18

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/187/ Build Number: 187 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #187 [Sandro Bonazzola] repos: adding cockpit-machines-ovirt [Evgheni Dereveanchin] Verify Jenkins user settings from global_setup ----------------- Failed Tests: ----------------- No tests ran.

1 31

Re: [ovirt-devel] [Announcement] Introducing Standard CI build summary
by Eyal Edri 31 May '18

31 May '18

Adding infra also. I think it would be great to do a tweet on it on @ovirt as well. Adding an example link from the Jenkins repo: http://jenkins.ovirt.org/job/jenkins_standard-check-patch/625/artifact/ci_b… On Wed, May 30, 2018 at 5:49 PM, Daniel Belenky <dbelenky(a)redhat.com> wrote: > Hi, > > On behalf of oVirt's CI team, I'm happy to announce the STDCI build > summary - > *We've used patternfly *[1] <http://www.patternfly.org/> to ensure a clean, > simple and elegant view of information for your builds. > The summary is available for STDCI V2 [2] projects and it is located > under *build-artifacts/ci_build_summary.html* > > > *[image: location.png]* > > > STDCI build summary is a single web page, generated dynamically for every > build on STDCI. > It visualizes all CI threads that ran for that build and features a set of > quick links. > > The main view shows a list of all threads with an indicator if that thread > failed or passed. > The quick links to the right of each thread lead to *log* and *artifacts* > of that thread only. > Note that *log* shows the output of your script only to ease debugging. > [image: threads_list.png] > > At the top right side, you will find a set of quick links for convenience: > > [image: menus.png] > > *Test results* (available if JUnit XML files were exported during the > build) leads to a summary of all JUnit test results that were collected > during the build. > *Test results analyzer *shows the history of test execution results in a > tabular format. > *Findbugs results *(available if Findbugs report was generated and > exported during the build) shows trend report for Findbugs. > *Full build log* shows the full log of all threads. This log is harder to > understand as it includes output from CI runtime environment as well as > from your scripts. > > *Rebuild (for GitHub PR)/Retrigger (for Gerrit patch): *Run the build > again. The new build will report and vote to Gerrit/GitHub with the new > result. > *View PR/patch: *Links back to the PR on GitHub or patchset page in > Gerrit. > > > [image: view_in_jenkins.png] > *View in Jenkins* will lead you back to the build view in Jenkins > > [image: view_in_blueocean.png] > *View in Blue Ocean *will lead you to the build view in Jenkins Blue > Ocean view > > STDCI Documentation https://ovirt-infra-docs.readthedocs. > io/en/latest/CI/Build_and_test_standards/index.html > > For any questions, don't hesitate to contact the CI team at #rhev-integ, > #rhev-dev > or view mail at infra(a)ovirt.org. > > Thanks, > Daniel. > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community- > guidelines/ > List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/ > message/XCRLR7XPCYBOMDT5MGBYHHI4FKO3427C/ > > -- Eyal edri MANAGER RHV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

1 0

[CQ]: 91826,4 (ovirt-setup-lib) failed "ovirt-4.1" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 91826,4 (ovirt-setup-lib) 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 change see: https://gerrit.ovirt.org/#/c/91826/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1796/

1 0

[CQ]: 91218,3 (vdsm) failed "ovirt-4.2" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 91218,3 (vdsm) 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 the change see: https://gerrit.ovirt.org/#/c/91218/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2128/

1 0

[CQ]: 91826,4 (ovirt-setup-lib) failed "ovirt-4.1" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 91826,4 (ovirt-setup-lib) 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 change see: https://gerrit.ovirt.org/#/c/91826/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.1_change-queue-tester/1794/

1 0

[JIRA] (OVIRT-2070) Please add Martin Necas to oVirt organization on github
by Martin Perina (oVirt JIRA) 31 May '18

31 May '18

Martin Perina created OVIRT-2070: ------------------------------------ Summary: Please add Martin Necas to oVirt organization on github Key: OVIRT-2070 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2070 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Martin Perina Assignee: infra Hi, could you please add Martin Necas (alias ocasek) to oVirt organization on github? Thanks Martin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[oVirt Jenkins] ovirt-system-tests_he-node-ng-suite-master - Build # 55 - Failure!
by jenkins＠jenkins.phx.ovirt.org 31 May '18

31 May '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/55/ Build Number: 55 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #55 [Dafna Ron] ovirt-4.1: removed broken links for 4.1 upgrade suites ----------------- Failed Tests: ----------------- No tests ran.

1 2

[oVirt CI] standard-enqueue - Build #13969 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 31 May '18

31 May '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/13969/ Build Name: #13969 Build Description: Gerrit: 91617 - ovirt-engine (4.2.3) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/91617 - title: build: post ovirt-engine-4.2.3.8 - project: ovirt-engine - branch: ovirt-engine-4.2.3.z - author: Sandro Bonazzola <sbonazzo(a)redhat.com>

1 0

Fwd: Fedora 26 End Of Life
by Sandro Bonazzola 31 May '18

31 May '18

FYI ---------- Forwarded message ---------- From: Mohan Boddu <mboddu(a)bhujji.com> Date: 2018-05-29 23:54 GMT+02:00 Subject: Fedora 26 End Of Life To: announce(a)lists.fedoraproject.org, devel-announce(a)lists.fedoraproject.org, test-announce(a)lists.fedoraproject.org As of the 29th of May 2018, Fedora 26 has reached its end of life for updates and support. No further updates, including security updates, will be available for Fedora 26. Fedora 27 will continue to receive updates until approximately one month after the release of Fedora 29. The maintenance schedule of Fedora releases is documented on the Fedora Project wiki [0]. The Fedora Project wiki also contains instructions [1] on how to upgrade from a previous release of Fedora to a version receiving updates. Regards, Mohan Boddu. [0]https://fedoraproject.org/wiki/Fedora_Release_Life_ Cycle#Maintenance_Schedule [1]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades _______________________________________________ devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org To unsubscribe send an email to devel-announce-leave(a)lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel- announce@lists.fedoraproject.org/message/XGG7GYUJN3VDA6HX4KJNFSKSQCGF2FMW/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

2 1

[JIRA] (OVIRT-2069) Switch the 'fabric-ovirt' project to STDCI V2
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

Barak Korren created OVIRT-2069: ----------------------------------- Summary: Switch the 'fabric-ovirt' project to STDCI V2 Key: OVIRT-2069 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2069 Project: oVirt - virtualization made easy Issue Type: Improvement Components: CI client projects Reporter: Barak Korren Assignee: infra We want to switch all project to STDCI V2. fabric-ovirt being an infra project, switching it should be quick and require no extra coordination. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2069) Switch the 'fabric-ovirt' project to STDCI V2
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2069?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2069: -------------------------------- Epic Link: OVIRT-400 > Switch the 'fabric-ovirt' project to STDCI V2 > --------------------------------------------- > > Key: OVIRT-2069 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2069 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: CI client projects > Reporter: Barak Korren > Assignee: infra > > We want to switch all project to STDCI V2. > fabric-ovirt being an infra project, switching it should be quick and require no extra coordination. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2068) Remove all FC26 slaves
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

Barak Korren created OVIRT-2068: ----------------------------------- Summary: Remove all FC26 slaves Key: OVIRT-2068 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2068 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra Fedora 26 has gone EOL, we need to remove the FC26 slaves and setup FC27/FC28 slaves instead. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2068) Remove all FC26 slaves
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2068?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2068: -------------------------------- Epic Link: OVIRT-403 > Remove all FC26 slaves > ---------------------- > > Key: OVIRT-2068 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2068 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Fedora 26 has gone EOL, we need to remove the FC26 slaves and setup FC27/FC28 slaves instead. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2067) Drop FC26 support from STDCI
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2067?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2067: ----------------------------------- Assignee: Barak Korren (was: infra) > Drop FC26 support from STDCI > ---------------------------- > > Key: OVIRT-2067 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2067 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: CI client projects, CI Mirrors, Jenkins Slaves, mock_runner > Reporter: Barak Korren > Assignee: Barak Korren > > Since Fedora 26 had gone EOL, we should drop support fro it in the CI system. > The main motivation for this is to clear the FC26 mirrors which take up ~134G > Things we need to take care of before being able to remove the mirros: > # Remove all FC26 slaves > # Remove all FC26 jobs > # Remove FC26 support from {{mock_runner.sh}} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2067) Drop FC26 support from STDCI
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2067?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2067: -------------------------------- Epic Link: OVIRT-400 > Drop FC26 support from STDCI > ---------------------------- > > Key: OVIRT-2067 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2067 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: CI client projects, CI Mirrors, Jenkins Slaves, mock_runner > Reporter: Barak Korren > Assignee: infra > > Since Fedora 26 had gone EOL, we should drop support fro it in the CI system. > The main motivation for this is to clear the FC26 mirrors which take up ~134G > Things we need to take care of before being able to remove the mirros: > # Remove all FC26 slaves > # Remove all FC26 jobs > # Remove FC26 support from {{mock_runner.sh}} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2067) Drop FC26 support from STDCI
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

Barak Korren created OVIRT-2067: ----------------------------------- Summary: Drop FC26 support from STDCI Key: OVIRT-2067 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2067 Project: oVirt - virtualization made easy Issue Type: Improvement Components: CI client projects, CI Mirrors, Jenkins Slaves, mock_runner Reporter: Barak Korren Assignee: infra Since Fedora 26 had gone EOL, we should drop support fro it in the CI system. The main motivation for this is to clear the FC26 mirrors which take up ~134G Things we need to take care of before being able to remove the mirros: # Remove all FC26 slaves # Remove all FC26 jobs # Remove FC26 support from {{mock_runner.sh}} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 91721, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

A system test invoked by the "ovirt-4.2" change queue including change 91721,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91638,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91638,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91721/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91638/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2122/

1 0

[CQ]: 86960,6 (ovirt-setup-lib) failed "ovirt-master" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 86960,6 (ovirt-setup-lib) 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 the change see: https://gerrit.ovirt.org/#/c/86960/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7987/

1 0

[CQ]: 91700, 2 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

A system test invoked by the "ovirt-4.2" change queue including change 91700,2 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 91638,2 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91638,2 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91700/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91638/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2115/

1 0

[CQ]: 91568, 10 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

A system test invoked by the "ovirt-master" change queue including change 91568,10 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 91571,9 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91571,9 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91568/10 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91571/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7981/

1 0

[CQ]: 72018, 1 (ovirt-engine-extension-logger-log4j) failed "ovirt-master" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 72018,1 (ovirt-engine-extension-logger-log4j) 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 the change see: https://gerrit.ovirt.org/#/c/72018/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7976/

1 0

[CQ]: 72008, 1 (ovirt-engine-extension-aaa-misc) failed "ovirt-master" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 72008,1 (ovirt-engine-extension-aaa-misc) 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 the change see: https://gerrit.ovirt.org/#/c/72008/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7970/

1 0

[CQ]: 87674, 2 (ovirt-engine-extension-aaa-jdbc) failed "ovirt-master" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 87674,2 (ovirt-engine-extension-aaa-jdbc) 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 the change see: https://gerrit.ovirt.org/#/c/87674/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7964/

1 0

[CQ]: 91599, 4 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

A system test invoked by the "ovirt-master" change queue including change 91599,4 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 91571,9 (ovirt-provider-ovn) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 91571,9 (ovirt-provider-ovn) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/91599/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/91571/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7958/

1 0