August 2019 - Infra - oVirt List Archives

[CQ]: 102923, 3 (ovirt-engine-nodejs-modules) failed "ovirt-4.2" system tests
by oVirt Jenkins 30 Aug '19

30 Aug '19

Change 102923,3 (ovirt-engine-nodejs-modules) 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/102923/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/4762/

1 0

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

30 Aug '19

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

1 0

oVirt infra daily report - unstable production jobs - 932
by jenkins＠jenkins.phx.ovirt.org 29 Aug '19

29 Aug '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/932//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 102941, 2 (otopi) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Aug '19

29 Aug '19

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

1 0

[CQ]: 102946, 1 (ovirt-host-deploy) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 29 Aug '19

29 Aug '19

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

1 0

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

29 Aug '19

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

1 0

[CQ]: 102745,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 29 Aug '19

29 Aug '19

Change 102745,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/102745/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/15608/

1 0

[JIRA] (OVIRT-1602) [RFE] allow passing a gerrit link to ovirt-system-tests_manual
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1602?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-1602: ----------------------------- Resolution: Fixed Status: Done (was: To Do) This is now supported by the new CLI tool written by [~accountid:557058:5b558a0f-5666-4b7f-a655-83e5cc3a5de0] > [RFE] allow passing a gerrit link to ovirt-system-tests_manual > -------------------------------------------------------------- > > Key: OVIRT-1602 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1602 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI > Reporter: Yedidyah Bar David > Assignee: infra > > Hi all, > How about $subject? > So that when ovirt-system-tests_manual sees a gerrit link supplied in > CUSTOM_REPOS, it will do by itself 'ci please build' (extra points for > checking if that's already done and reusing) and use the resultant > build as if that build itself was supplied in CUSTOM_REPOS, thus > freeing the user from doing that? I find myself many times running 'ci > please build' only to later wait until it finished and then pass that > to ovirt-system-tests_manual. For projects that are very quick to > build, that's a bit tedious, but not too much. But for engine builds, > that take somewhat longer, I often forget this and come back later. It > would have been nice to be able to do this in a "single shot". > Thanks, > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

[JIRA] (OVIRT-2599) Investigate sync between JIRA cloud to JIRA server
by Eyal Edri (oVirt JIRA) 29 Aug '19

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2599?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2599: -------------------------------- Assignee: Anton Marchukov (was: infra) > Investigate sync between JIRA cloud to JIRA server > -------------------------------------------------- > > Key: OVIRT-2599 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2599 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Eyal Edri > Assignee: Anton Marchukov > > We would like to converge on using a single JIRA board to show all our issues. > There are some solution available, more info the following links; > https://community.atlassian.com/t5/Jira-questions/Sync-between-JIRA-Cloud-a… > from that blog: > https://marketplace.atlassian.com/apps/1215199/backbone-issue-sync-for-jira… > https://confluence.atlassian.com/jiracoreserver073/linking-issues-861257339… > https://confluence.atlassian.com/applinks/application-links-documentation-1… > https://www.connectall.com/ > https://marketplace.atlassian.com/apps/1215199/backbone-issue-sync-for-jira… > There are other options, shown up on a quick search. > Once we find a reasonable plugin, we can ask PnT to purchase and install it on the d/s instance. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

1 0

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

29 Aug '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2714?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2714: ----------------------------- 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#100108)

1 0