- Infra - oVirt List Archives

[CQ]: 99295,1 (cockpit-ovirt) failed "ovirt-master" system tests
by oVirt Jenkins 11 Apr '19

11 Apr '19

Change 99295,1 (cockpit-ovirt) 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/99295/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13784/

1 0

oVirt infra daily report - unstable production jobs - 791
by jenkins＠jenkins.phx.ovirt.org 10 Apr '19

10 Apr '19

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/791//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: bc61fb2 (v2v-conversion-host) failed "ovirt-4.3" system tests
by oVirt Jenkins 10 Apr '19

10 Apr '19

Change bc61fb2 (v2v-conversion-host) is probably the reason behind recent system test failures in the "ovirt-4.3" 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://github.com/oVirt/v2v-conversion-host/commit/bc61fb287ba4a9ddae10e56… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/640/

1 0

[CQ]: bc61fb2 (v2v-conversion-host) failed "ovirt-master" system tests
by oVirt Jenkins 10 Apr '19

10 Apr '19

Change bc61fb2 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/bc61fb287ba4a9ddae10e56… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13780/

1 0

[CQ]: 6942b0e (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.3" system tests
by oVirt Jenkins 10 Apr '19

10 Apr '19

Change 6942b0e (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-4.3" 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/6942b0e80… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/639/

1 0

[CQ]: 99301,3 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 10 Apr '19

10 Apr '19

Change 99301,3 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99301/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/635/

1 0

[CQ]: 99196,5 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 10 Apr '19

10 Apr '19

Change 99196,5 (vdsm) 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/99196/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13777/

1 0

[CQ]: 99284,1 (ovirt-release) failed "ovirt-4.3" system tests
by oVirt Jenkins 10 Apr '19

10 Apr '19

Change 99284,1 (ovirt-release) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99284/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/632/

1 0

[CQ]: 99194,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 10 Apr '19

10 Apr '19

Change 99194,2 (vdsm) 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/99194/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13773/

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Barak Korren (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2714: ------------------------------------- [~eedri] we can probably move the manual job to use containers if we didn't already, that aught to let it have more executors aviabale. [~gbenhaim(a)redhat.com] [~dbelenky(a)redhat.com] WDYT? [~mskrivanek] please note that moving into containers will have about 30% impact on the job performance, so we're paying in latency for greater throughput... > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Eyal Edri (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2714: ---------------------------------- We have 5 servers, which are shared between CQ, OST check-patch and nightly OST Jobs. so not so much. Is running OST Manually is an option? you can run the same way it run on the manual job. If we see it's not enough, maybe we consider paying for renting external bare metals, or we can also look into moving another server to run inside OpenShift to run more load as I've asked [~gbenhaim(a)redhat.com] and [~dbelenky(a)redhat.com] same as KubeVirt runs. Why do you think it's not available? as I said, its probably being taken by CQ or OST check-patch... eventually we have a limited amount of hosts, so i'm not sure there are ideal hosts > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-2714: ----------------------------------------- I see. So how many we have? One? Can it be shared with other hosts? And even if we have just one right now - why is it not available? It's happening relatively frequently (roughly once in two weeks from what I've seen) > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Eyal Edri (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2714: ---------------------------------- The manual job has already 10 available executors: job-template: name: '{project}_manual' project: '{project}' concurrent: true properties: - build-discarder: days-to-keep: 14 - throttle: enabled: true option: project max-total: 10 The fact that jobs are waiting in queue means there aren't enough hosts to run the tests, something that isn't easily solvable without buying new hardware or perhaps moving the manual job to run on containers instead of single bare metals servers. [~gbenhaim@redhat.com][~dbelenky@redhat.com] how much time will it take to move the manual OST Job to run on containers, something that might help here? > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek updated OVIRT-2714: ------------------------------------ Status: To Do (was: In Progress) > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek reopened OVIRT-2714: ------------------------------------- > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek edited comment on OVIRT-2714 at 4/10/19 10:04 AM: ------------------------------------------------------------------- the intent of the original ticket to solve manual OST, but it only solves building artifacts. e still need more concurrent (or at least 1!!!) worker for the actual OST run was (Author: mskrivanek): actually, now that i read the description again. it was the intent of the original ticket to solve manual OST...so the original ticket is the right one > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek updated OVIRT-2714: ------------------------------------ Resolution: Duplicate Status: Done (was: To Do) > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-2714: ----------------------------------------- actually, now that i read the description again. it was the intent of the original ticket to solve manual OST...so the original ticket is the right one > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek updated OVIRT-2714: ------------------------------------ Description: This one is about manual OST runs cloned from OVIRT-2704 --- We started to use this job to build artifacts for running OST. Looks like this job is limited to one concurrent job, which make it less useful than it could be. If we don't make it easy to run OST, people will not run it, and the change queue will break. Please change the limit to use the same limit used for regular builds. We seem to be able to create more then 10 concurrent builds by uploading patches to gerrit. The manual runner should this as well. Nir was: We started to use this job to build artifacts for running OST. Looks like this job is limited to one concurrent job, which make it less useful than it could be. If we don't make it easy to run OST, people will not run it, and the change queue will break. Please change the limit to use the same limit used for regular builds. We seem to be able to create more then 10 concurrent builds by uploading patches to gerrit. The manual runner should this as well. Nir > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > This one is about manual OST runs > cloned from OVIRT-2704 > --- > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Michal Skrivanek updated OVIRT-2714: ------------------------------------ Summary: Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs (was: CLONE - Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs) > Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs > ------------------------------------------------------------------------------------------- > > Key: OVIRT-2714 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Michal Skrivanek > Assignee: infra > > We started to use this job to build artifacts for running OST. > Looks like this job is limited to one concurrent job, which make it less > useful than > it could be. > If we don't make it easy to run OST, people will not run it, and the change > queue > will break. > Please change the limit to use the same limit used for regular builds. We > seem to be > able to create more then 10 concurrent builds by uploading patches to > gerrit. The manual > runner should this as well. > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2714) CLONE - Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs
by Michal Skrivanek (oVirt JIRA) 10 Apr '19

10 Apr '19

Michal Skrivanek created OVIRT-2714: --------------------------------------- Summary: CLONE - Increase limits on concurrent https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ jobs Key: OVIRT-2714 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2714 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Michal Skrivanek Assignee: infra We started to use this job to build artifacts for running OST. Looks like this job is limited to one concurrent job, which make it less useful than it could be. If we don't make it easy to run OST, people will not run it, and the change queue will break. Please change the limit to use the same limit used for regular builds. We seem to be able to create more then 10 concurrent builds by uploading patches to gerrit. The manual runner should this as well. Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2713) Package does not match intended download on PHX mirror
by Evgheni Dereveanchin (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2713?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2713: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Package does not match intended download on PHX mirror > ------------------------------------------------------ > > Key: OVIRT-2713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2713 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > I was working on updating some nodes and hit an issue that was reported before in CI. Basically, a package fails to install when running "yum update" with the following error: > Error downloading packages: > polkit-0.112-18.el7_6.1.x86_64: failed to retrieve Packages/polkit-0.112-18.el7_6.1.x86_64.rpm from centos-updates-el7 > error was [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=centos-updates-el7 clean metadata > Last time I checked the file was intact on the mirror so it may be a sign of metadata corruption on the snapshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2713) Package does not match intended download on PHX mirror
by Evgheni Dereveanchin (oVirt JIRA) 10 Apr '19

10 Apr '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2713?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2713: --------------------------------------------- The exact URL that fails is: http://mirrors.phx.ovirt.org/repos/yum/centos-updates-el7/base/Packages/pol… Downloading this file produces an md5sum of 79c1fa6804307bfc54833c880743c358 which matches the file from an upstream mirror: http://mirror.centos.org/centos/7/updates/x86_64/Packages/polkit-0.112-18.e… Running "rpm -Uvh" on the downloaded RPM does not produce any warnings either so it is intact. > Package does not match intended download on PHX mirror > ------------------------------------------------------ > > Key: OVIRT-2713 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2713 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > I was working on updating some nodes and hit an issue that was reported before in CI. Basically, a package fails to install when running "yum update" with the following error: > Error downloading packages: > polkit-0.112-18.el7_6.1.x86_64: failed to retrieve Packages/polkit-0.112-18.el7_6.1.x86_64.rpm from centos-updates-el7 > error was [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=centos-updates-el7 clean metadata > Last time I checked the file was intact on the mirror so it may be a sign of metadata corruption on the snapshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2713) Package does not match intended download on PHX mirror
by Evgheni Dereveanchin (oVirt JIRA) 10 Apr '19

10 Apr '19

Evgheni Dereveanchin created OVIRT-2713: ------------------------------------------- Summary: Package does not match intended download on PHX mirror Key: OVIRT-2713 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2713 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra I was working on updating some nodes and hit an issue that was reported before in CI. Basically, a package fails to install when running "yum update" with the following error: Error downloading packages: polkit-0.112-18.el7_6.1.x86_64: failed to retrieve Packages/polkit-0.112-18.el7_6.1.x86_64.rpm from centos-updates-el7 error was [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=centos-updates-el7 clean metadata Last time I checked the file was intact on the mirror so it may be a sign of metadata corruption on the snapshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JENKINS] Failed to setup proejct vdsm_standard-check-patch
by jenkins＠jenkins.phx.ovirt.org 10 Apr '19

10 Apr '19

Failed to run project_setup.sh for: #4674 vdsm [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on vm0042.workers-phx.ovirt.org.

1 0

[CQ]: 98922, 8 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 10 Apr '19

10 Apr '19

A system test invoked by the "ovirt-4.3" change queue including change 98922,8 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 99237,2 (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 99237,2 (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/98922/8 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/99237/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/623/

1 0

[CQ]: 98922, 8 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 10 Apr '19

10 Apr '19

Change 98922,8 (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/98922/8 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13770/

1 0

oVirt infra daily report - unstable production jobs - 790
by jenkins＠jenkins.phx.ovirt.org 09 Apr '19

09 Apr '19

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/790//artifact/exported-a… Cheers, Jenkins

1 0

Build failed in Jenkins: system-sync_mirrors-glusterfs-5-el7-x86_64 #239
by jenkins＠jenkins.phx.ovirt.org 09 Apr '19

09 Apr '19

See <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-5-el7-x86_64/239…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-glusterfs-5-el7-x86_64/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision a6f2e271684c62613aab969ba1c988e4b85a51e8 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f a6f2e271684c62613aab969ba1c988e4b85a51e8 Commit message: "Make standard-manual-runner run concurrently" > git rev-list --no-walk a6f2e271684c62613aab969ba1c988e4b85a51e8 # timeout=10 [system-sync_mirrors-glusterfs-5-el7-x86_64] $ /bin/bash -xe /tmp/jenkins3715944413563678211.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf + MIRRORS_MP_BASE=/var/www/html/repos + MIRRORS_HTTP_BASE=http://mirrors.phx.ovirt.org/repos + MIRRORS_CACHE=/home/jenkins/mirrors_cache + MAX_LOCK_ATTEMPTS=120 + LOCK_WAIT_INTERVAL=5 + LOCK_BASE=/home/jenkins + OLD_MD_TO_KEEP=100 + HTTP_SELINUX_TYPE=httpd_sys_content_t + HTTP_FILE_MODE=644 + main resync_yum_mirror glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf + local command=resync_yum_mirror + command_args=("${@:2}") + local command_args + cmd_resync_yum_mirror glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf + local repo_name=glusterfs-5-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local sync_needed + mkdir -p /home/jenkins/mirrors_cache + verify_repo_fs glusterfs-5-el7 yum + local repo_name=glusterfs-5-el7 + local repo_type=yum + sudo install -o jenkins -d /var/www/html/repos/yum /var/www/html/repos/yum/glusterfs-5-el7 /var/www/html/repos/yum/glusterfs-5-el7/base + check_yum_sync_needed glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf sync_needed + local repo_name=glusterfs-5-el7 + local repo_archs=x86_64 + local reposync_conf=jenkins/data/mirrors-reposync.conf + local p_sync_needed=sync_needed + local reposync_out + echo 'Checking if mirror needs a resync' Checking if mirror needs a resync + rm -rf /home/jenkins/mirrors_cache/glusterfs-5-el7 ++ IFS=, ++ echo x86_64 + for arch in '$(IFS=,; echo $repo_archs)' ++ run_reposync glusterfs-5-el7 x86_64 jenkins/data/mirrors-reposync.conf --urls --quiet ++ local repo_name=glusterfs-5-el7 ++ local repo_arch=x86_64 ++ local reposync_conf=jenkins/data/mirrors-reposync.conf ++ extra_args=("${@:4}") ++ local extra_args ++ reposync --config=jenkins/data/mirrors-reposync.conf --repoid=glusterfs-5-el7 --arch=x86_64 --cachedir=/home/jenkins/mirrors_cache --download_path=/var/www/html/repos/yum/glusterfs-5-el7/base --norepopath --newest-only --urls --quiet Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/glusterfs-5-el7/gen error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/glusterfs-5-el7/gen' + reposync_out= Build step 'Execute shell' marked build as failure

1 1

[CQ]: 7431819 (v2v-conversion-host) failed "ovirt-4.3" system tests
by oVirt Jenkins 09 Apr '19

09 Apr '19

Change 7431819 (v2v-conversion-host) is probably the reason behind recent system test failures in the "ovirt-4.3" 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://github.com/oVirt/v2v-conversion-host/commit/74318192450d80f6c61bf7d… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/620/

1 0

[JIRA] (OVIRT-2712) ovirt-engine-sdk-go merge is not triggering jenkins CI
by sbonazzo (oVirt JIRA) 09 Apr '19

09 Apr '19

sbonazzo created OVIRT-2712: ------------------------------- Summary: ovirt-engine-sdk-go merge is not triggering jenkins CI Key: OVIRT-2712 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2712 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra https://jenkins.ovirt.org/job/oVirt_ovirt-engine-sdk-go_standard-on-ghpush/ has no jobs built. Can you please check what's wrong there? Thanks -- SANDRO BONAZZOLA MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[CQ]: 98789, 16 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 09 Apr '19

09 Apr '19

A system test invoked by the "ovirt-4.3" change queue including change 98789,16 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 99237,2 (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 99237,2 (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/98789/16 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/99237/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/618/

1 0

[CQ]: 99283,1 (ovirt-release) failed "ovirt-4.3" system tests
by oVirt Jenkins 09 Apr '19

09 Apr '19

Change 99283,1 (ovirt-release) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99283/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/615/

1 0

[CQ]: 99260,1 (vdsm) failed "ovirt-4.3" system tests
by oVirt Jenkins 09 Apr '19

09 Apr '19

Change 99260,1 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99260/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/613/

1 0

[CQ]: 99274, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Apr '19

08 Apr '19

A system test invoked by the "ovirt-master" change queue including change 99274,1 (ovirt-engine-metrics) failed. However, this change seems not to be the root cause for this failure. Change 99273,1 (ovirt-engine-metrics) 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 99273,1 (ovirt-engine-metrics) 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/99274/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/99273/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13762/

1 0

[CQ]: 99273, 1 (ovirt-engine-metrics) failed "ovirt-master" system tests
by oVirt Jenkins 08 Apr '19

08 Apr '19

Change 99273,1 (ovirt-engine-metrics) 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/99273/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13761/

1 0

oVirt infra daily report - unstable production jobs - 789
by jenkins＠jenkins.phx.ovirt.org 08 Apr '19

08 Apr '19

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/789//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 99274,1 (ovirt-engine-metrics) failed "ovirt-4.3" system tests
by oVirt Jenkins 08 Apr '19

08 Apr '19

Change 99274,1 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99274/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/610/

1 0

[CQ]: 99270,5 (ovirt-engine-metrics) failed "ovirt-4.3" system tests
by oVirt Jenkins 08 Apr '19

08 Apr '19

Change 99270,5 (ovirt-engine-metrics) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99270/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/609/

1 0

[CQ]: 99243,2 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 08 Apr '19

08 Apr '19

Change 99243,2 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99243/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/606/

1 0

[CQ]: 99116,4 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 08 Apr '19

08 Apr '19

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

1 0

[CQ]: 9f526be (ovirt-ansible-hosted-engine-setup) failed "ovirt-4.3" system tests
by oVirt Jenkins 08 Apr '19

08 Apr '19

Change 9f526be (ovirt-ansible-hosted-engine-setup) is probably the reason behind recent system test failures in the "ovirt-4.3" 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://github.com/oVirt/ovirt-ansible-hosted-engine-setup/commit/9f526be1f… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/605/

1 0

[CQ]: 99237,2 (ovirt-provider-ovn) failed "ovirt-4.3" system tests
by oVirt Jenkins 08 Apr '19

08 Apr '19

Change 99237,2 (ovirt-provider-ovn) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99237/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/604/

1 0

[CQ]: 99260,1 (vdsm) failed "ovirt-4.3" system tests
by oVirt Jenkins 08 Apr '19

08 Apr '19

Change 99260,1 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99260/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/602/

1 0

[CQ]: 99233,1 (vdsm) failed "ovirt-4.3" system tests
by oVirt Jenkins 08 Apr '19

08 Apr '19

Change 99233,1 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.3" 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/99233/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/596/

1 0

[CQ]: 99193, 1 (ovirt-provider-ovn) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Apr '19

08 Apr '19

A system test invoked by the "ovirt-4.3" change queue including change 99193,1 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 98722,4 (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 98722,4 (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/99193/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/98722/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/594/

1 0

[CQ]: 99193, 1 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 08 Apr '19

08 Apr '19

A system test invoked by the "ovirt-master" change queue including change 99193,1 (ovirt-provider-ovn) failed. However, this change seems not to be the root cause for this failure. Change 98722,4 (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 98722,4 (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/99193/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/98722/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13748/

1 0

[CQ]: 66d324e (ovirt-web-ui) failed "ovirt-master" system tests
by oVirt Jenkins 08 Apr '19

08 Apr '19

Change 66d324e (ovirt-web-ui) 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://github.com/oVirt/ovirt-web-ui/commit/66d324e53b9ff10f565d323cc02f73… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13747/

1 0

[CQ]: 66d324e (ovirt-web-ui) failed "ovirt-4.2" system tests
by oVirt Jenkins 08 Apr '19

08 Apr '19

Change 66d324e (ovirt-web-ui) 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://github.com/oVirt/ovirt-web-ui/commit/66d324e53b9ff10f565d323cc02f73… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4180/

1 0

oVirt infra daily report - unstable production jobs - 788
by jenkins＠jenkins.phx.ovirt.org 07 Apr '19

07 Apr '19

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/788//artifact/exported-a… Cheers, Jenkins

1 0