December 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2617) Allow rerunning only failed test lanes
by Eyal Edri (oVirt JIRA) 31 Dec '18

31 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2617?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2617: ---------------------------------- We will need to asses how much value/improvement it will bring to the CI and then target to one of the future sprints. In any case we'll track it here: https://trello.com/c/4syVDHiD > Allow rerunning only failed test lanes > -------------------------------------- > > Key: OVIRT-2617 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2617 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Roman Mohr > Assignee: infra > > Hi, > In KubeVirt we run a lot of differnent test lanes. Even if our tests are > written in a good way and if the underlying CI infra is stable and fast, > there will always be cases where for-whatever reason one or two tests can > fail out of hundreds in a lane. > It would be very helpful if we could have a /retest command or something > similar where only failed lanes are re-run. That would be similar to how it > is handled in Kubernetes. > Right now it is an all-or-nothing thing. > What I would expect, is that it is still possible to see the test history > somewhere then (e.g. the first two attempts where it failed and then the > third one where it succeeds). > Best Regards, > Roman -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)

1 0

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
by Daniel Belenky (oVirt JIRA) 31 Dec '18

31 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2638?page=com.atlassian.jira.… ] Daniel Belenky edited comment on OVIRT-2638 at 12/31/18 12:47 PM: ------------------------------------------------------------------ I've cleaned the host, and it is not up and running. The problem was that due filled disk, there were stuck VMs there that prevented the host from being cleaned up. was (Author: dbelenky(a)redhat.com) I've cleaned the host, and it is not up and running. > ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days > ------------------------------------------------------------------------ > > Key: OVIRT-2638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Daniel Belenky > > Started 2 days 11 hr ago > Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or > <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> > https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)

1 0

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
by Daniel Belenky (oVirt JIRA) 31 Dec '18

31 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2638?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2638: ---------------------------------- Resolution: Fixed Status: Done (was: To Do) > ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days > ------------------------------------------------------------------------ > > Key: OVIRT-2638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Daniel Belenky > > Started 2 days 11 hr ago > Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or > <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> > https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)

1 0

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
by Daniel Belenky (oVirt JIRA) 31 Dec '18

31 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2638?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2638: --------------------------------------- I've cleaned the host, and it is not up and running. > ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days > ------------------------------------------------------------------------ > > Key: OVIRT-2638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Daniel Belenky > > Started 2 days 11 hr ago > Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or > <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> > https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)

1 0

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
by Daniel Belenky (oVirt JIRA) 31 Dec '18

31 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2638?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2638: --------------------------------------- [~lmilbaum(a)redhat.com] There is no service that sends an email but those VMs are managed by our oVirt engine phx instance [here|https://engine-phx.ovirt.org] so the disk can be monitored from there. > ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days > ------------------------------------------------------------------------ > > Key: OVIRT-2638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Daniel Belenky > > Started 2 days 11 hr ago > Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or > <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> > https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)

1 0

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
by Daniel Belenky (oVirt JIRA) 31 Dec '18

31 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2638?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2638: ------------------------------------- Assignee: Daniel Belenky (was: infra) > ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days > ------------------------------------------------------------------------ > > Key: OVIRT-2638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Daniel Belenky > > Started 2 days 11 hr ago > Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or > <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> > https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)

1 0

[oVirt Jenkins] ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 - Build # 33 - Failure!
by jenkins＠jenkins.phx.ovirt.org 31 Dec '18

31 Dec '18

Project: http://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x… Build: http://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-x… Build Number: 33 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #33 [Sandro Bonazzola] automation: add devices for qemu performances [Sandro Bonazzola] ovirt-hosted-engine-ha: drop 3.6 jobs [Sandro Bonazzola] ovirt-log-collector: drop obsolete jobs [Sandro Bonazzola] ovirt-hosted-engine-setup: drop obsolete jobs [Sandro Bonazzola] ovirt-release: drop 3.6 jobs [Sandro Bonazzola] ovirt-engine-cli: drop obsolete jobs [Sandro Bonazzola] vdsm-jsonrpc-java: drop obsolete jobs [Sandro Bonazzola] ovirt-scheduler-proxy: drop obsolete jobs [Sandro Bonazzola] ovirt-engine-sdk-java: drop obsolete jobs [Sandro Bonazzola] ovirt-engine-sdk: drop obsolete jobs [Dafna Ron] jenkins: adding inject mirror for opstool-release ----------------- Failed Tests: ----------------- No tests ran.

1 6

[JIRA] (OVIRT-2639) Add support to upstream sources to be able to test github PR
by Shirly Radco (oVirt JIRA) 31 Dec '18

31 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2639?page=com.atlassian.jira.… ] Shirly Radco commented on OVIRT-2639: ------------------------------------- [~eedri] I already added the upstream sources and they work as expected. From what I understand, it is still not possible to be able to build in jenkins using a PR in the github repo. Opened this request for a new feature after discussion with [~dbelenky(a)redhat.com] > Add support to upstream sources to be able to test github PR > ------------------------------------------------------------ > > Key: OVIRT-2639 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2639 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > I added to ovirt-engine-metrics a github repo as upstream source. > I would like to be able to test github PR with in jenkins. > Best regards, > -- > SHIRLY RADCO > BI SENIOR SOFTWARE ENGINEER > Red Hat Israel <https://www.redhat.com/> > <https://red.ht/sig> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)

1 0

[JIRA] (OVIRT-2638) ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days
by Liora Milbaum (oVirt JIRA) 31 Dec '18

31 Dec '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2638?page=com.atlassian.jira.… ] Liora Milbaum commented on OVIRT-2638: -------------------------------------- [~dbelenky(a)redhat.com] Do we have a service which tracks the slave disk space. And, if it reaches a certain threshold... performs some remediation steps? > ovirt-node-ng-image_4.3_build-artifacts-fc28-x86_64 #39 stuck for 2 days > ------------------------------------------------------------------------ > > Key: OVIRT-2638 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2638 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > Started 2 days 11 hr ago > Build has been executing for 2 days 11 hr on vm0038.workers-phx.ovirt.or > <https://jenkins.ovirt.org/computer/vm0038.workers-phx.ovirt.org> > https://jenkins.ovirt.org/job/ovirt-node-ng-image_4.3_build-artifacts-fc28-… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100096)

1 0

[oVirt Jenkins] ovirt-appliance_ovirt-4.3_build-artifacts-el7-x86_64 - Build # 44 - Failure!
by jenkins＠jenkins.phx.ovirt.org 31 Dec '18

31 Dec '18

Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-el7-… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.3_build-artifacts-el7-… Build Number: 44 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #44 [Daniel Belenky] Add el7-runner-node container image [Daniel Belenky] Add el7-loader-node container [Gal Ben Haim] Add "org" attribute to the Project class [Gal Ben Haim] Associate jobs from "kubevirt" org with a specific label [Eyal Edri] update coverity scan email to dfediuck(a)redhat.com [Yuval Turgeman] build: change root fs to be a logical volume ----------------- Failed Tests: ----------------- No tests ran.

1 1