April 2019 - Infra - oVirt List Archives

[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