- Infra - oVirt List Archives

[CQ]: 97534, 2 (ovirt-node-ng-image) failed "ovirt-master" system tests
by oVirt Jenkins 07 Feb '19

07 Feb '19

Change 97534,2 (ovirt-node-ng-image) 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/97534/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12750/

3 2

[CQ]: 97484,5 (ovirt-provider-ovn) failed "ovirt-4.2" system tests
by oVirt Jenkins 07 Feb '19

07 Feb '19

Change 97484,5 (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/97484/5 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3839/

2 1

[CQ]: 93ba412 (ovirt-ansible-v2v-conversion-host) failed "ovirt-master" system tests
by oVirt Jenkins 07 Feb '19

07 Feb '19

Change 93ba412 (ovirt-ansible-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/ovirt-ansible-v2v-conversion-host/commit/93ba4120b… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12756/

2 1

[CQ]: 97454, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '19

07 Feb '19

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

1 0

NOTICE: ovirt-web-ui is missing from master CQ tested repos causing all project to fail CQ master
by Dafna Ron 07 Feb '19

07 Feb '19

Hi, CQ master is failing on missing ovirt-web-ui package. Ehud is checking why the package is missing but we may need to re-trigger a new build for this package to re-build it in CQ. For now, until we have a new package moved to tested we are failing CQ ERROR: ---> Package python-linecache2.noarch 0:1.0.0-1.el7 will be installed --> Finished Dependency Resolution Error: Package: ovirt-engine-4.3.0.5-0.0.master.20190205084851.gitaaebfc9.el7.noarch (ovirt-master-tested-el7) Requires: ovirt-web-ui You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest + : + lago copy-from-vm vm-01 /tmp/ovirt-master.repo.in.modified . Thanks, Dafna

5 9

[JIRA] (OVIRT-2672) Nicer URLs in jenkins
by Barak Korren (oVirt JIRA) 06 Feb '19

06 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2672?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2672: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) > Nicer URLs in jenkins > --------------------- > > Key: OVIRT-2672 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2672 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Jenkinks OST URLs are too ugly. > When looking for OST manual job, we go to: > https://jenkins.ovirt.org/view/oVirt%20system%20tests/ > This should be something like: > https://jenkins.ovirt.org/view/ost/ > Or > https://jenkins.ovirt.org/view/ovirt-system-tests > Then we click on "ovirt-system-tests_manual" which links to: > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > Here we can easily make the url much nicer by modifying the URL to: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ > Now we can start a build, and easily get a nice URL for the build > to paste on gerrit, like: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4025/ > So this looks like an easy fix, make the links point to > https://jenkins.ovirt.org/job/<job name> > Why should we make URLs nicer? > Ugly URLs are a broken window: > https://en.wikipedia.org/wiki/Broken_windows_theory > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2672) Nicer URLs in jenkins
by Barak Korren (oVirt JIRA) 06 Feb '19

06 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2672?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2672: ------------------------------------- As you already wrote, if you go the the job directly you get a nice URL without the space escapes. (%20): https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ We can't change the view url - Jenkins simply uses the title of the view for the URL, since the title contains spaces, you get %20 chars in the URL. IMO most URLs in Jenkins are nice enough already. Also, you can customize your own home screen to point directly to the jobs you need and hide all the other views, then you can do what you want with the URLs. Quite frankly we have bigger fish to fry, closing this ticket. > Nicer URLs in jenkins > --------------------- > > Key: OVIRT-2672 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2672 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Jenkinks OST URLs are too ugly. > When looking for OST manual job, we go to: > https://jenkins.ovirt.org/view/oVirt%20system%20tests/ > This should be something like: > https://jenkins.ovirt.org/view/ost/ > Or > https://jenkins.ovirt.org/view/ovirt-system-tests > Then we click on "ovirt-system-tests_manual" which links to: > https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… > Here we can easily make the url much nicer by modifying the URL to: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/ > Now we can start a build, and easily get a nice URL for the build > to paste on gerrit, like: > https://jenkins.ovirt.org/job/ovirt-system-tests_manual/4025/ > So this looks like an easy fix, make the links point to > https://jenkins.ovirt.org/job/<job name> > Why should we make URLs nicer? > Ugly URLs are a broken window: > https://en.wikipedia.org/wiki/Broken_windows_theory > Nir -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97456, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Feb '19

06 Feb '19

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

1 0

[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build # 472 - Failure!
by jenkins＠jenkins.phx.ovirt.org 06 Feb '19

06 Feb '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/472/ Build Number: 472 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #472 [Gal Ben Haim] automation: Move OST to run on STDCI containers [Sandro Bonazzola] vcredist-x86: move to oVirt stdci v2 ----------------- Failed Tests: ----------------- No tests ran.

1 5

[oVirt Jenkins] ovirt-system-tests_compat-4.1-suite-master - Build # 472 - Failure!
by jenkins＠jenkins.phx.ovirt.org 06 Feb '19

06 Feb '19

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.1-suite-master/472/ Build Number: 472 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #472 [Gal Ben Haim] automation: Move OST to run on STDCI containers [Sandro Bonazzola] vcredist-x86: move to oVirt stdci v2 ----------------- Failed Tests: ----------------- No tests ran.

1 5