March 2019 - Infra - oVirt List Archives

[JIRA] (OVIRT-2706) how do we cache docker images in OST?
by Barak Korren (oVirt JIRA) 25 Mar '19

25 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2706?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2706: -------------------------------- Issue Type: Improvement (was: By-EMAIL) > how do we cache docker images in OST? > ------------------------------------- > > Key: OVIRT-2706 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2706 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Greg Sheremeta > Assignee: infra > > Currently we download the selenium grid containers on every run of 008 > basic ui sanity, and the containers are huge. Can we cache them somewhere > so OST doesn't need to download them every time? Please advise how and what > we need to do to enable this. Thanks! > Best wishes, > Greg > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2706) how do we cache docker images in OST?
by Barak Korren (oVirt JIRA) 25 Mar '19

25 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2706?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2706: ------------------------------------- [~gshereme(a)redhat.com] Same way we cache any container - we have a whitelist of container images that the system leaves behind on the node it ran on. If you can provide us with the list of selenium images we can make sure they are kept. > how do we cache docker images in OST? > ------------------------------------- > > Key: OVIRT-2706 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2706 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Currently we download the selenium grid containers on every run of 008 > basic ui sanity, and the containers are huge. Can we cache them somewhere > so OST doesn't need to download them every time? Please advise how and what > we need to do to enable this. Thanks! > Best wishes, > Greg > -- > GREG SHEREMETA > SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX > Red Hat NA > <https://www.redhat.com/> > gshereme(a)redhat.com IRC: gshereme > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[CQ]: d117169 (v2v-conversion-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Mar '19

24 Mar '19

A system test invoked by the "ovirt-master" change queue including change d117169 (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change 48aed50 (v2v-conversion-host) 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 48aed50 (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/d117169276558f31d545682… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/48aed50ea69389a7443c8ad… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13536/

1 0

[CQ]: d117169 (v2v-conversion-host) failed "ovirt-4.3" system tests
by oVirt Jenkins 24 Mar '19

24 Mar '19

Change d117169 (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/d117169276558f31d545682… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/352/

1 0

[CQ]: 48aed50 (v2v-conversion-host) failed "ovirt-master" system tests
by oVirt Jenkins 24 Mar '19

24 Mar '19

Change 48aed50 (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/48aed50ea69389a7443c8ad… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13535/

1 0

oVirt infra daily report - unstable production jobs - 774
by jenkins＠jenkins.phx.ovirt.org 24 Mar '19

24 Mar '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/774//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 19dc243 (v2v-conversion-host) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 24 Mar '19

24 Mar '19

A system test invoked by the "ovirt-4.3" change queue including change 19dc243 (v2v-conversion-host) failed. However, this change seems not to be the root cause for this failure. Change b704bcf (v2v-conversion-host) 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 b704bcf (v2v-conversion-host) 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://github.com/oVirt/v2v-conversion-host/commit/19dc243fc7a9b8aced9f315… For further details about the change that seems to be the root cause behind the testing failures see: https://github.com/oVirt/v2v-conversion-host/commit/b704bcfdb41dab5496f1d09… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/349/

1 0

[JIRA] (OVIRT-2706) how do we cache docker images in OST?
by Greg Sheremeta (oVirt JIRA) 24 Mar '19

24 Mar '19

Greg Sheremeta created OVIRT-2706: ------------------------------------- Summary: how do we cache docker images in OST? Key: OVIRT-2706 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2706 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra Currently we download the selenium grid containers on every run of 008 basic ui sanity, and the containers are huge. Can we cache them somewhere so OST doesn't need to download them every time? Please advise how and what we need to do to enable this. Thanks! Best wishes, Greg -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA <https://www.redhat.com/> gshereme(a)redhat.com IRC: gshereme <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100099)

1 0

[JIRA] (OVIRT-2704) Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs
by Daniel Belenky (oVirt JIRA) 24 Mar '19

24 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2704?page=com.atlassian.jira.… ] Daniel Belenky edited comment on OVIRT-2704 at 3/24/19 4:27 PM: ---------------------------------------------------------------- You need to update the throttle secion of the "{project}_manual" template in `jobs/confs/yaml/templates/system_tests_templates.yaml` was (Author: dbelenky(a)redhat.com) You need to update the throttle secion of the {project}_manual template in `jobs/confs/yaml/templates/system_tests_templates.yaml` > Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs > ---------------------------------------------------------------------------------------- > > Key: OVIRT-2704 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2704 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > 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-2704) Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs
by Daniel Belenky (oVirt JIRA) 24 Mar '19

24 Mar '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2704?page=com.atlassian.jira.… ] Daniel Belenky edited comment on OVIRT-2704 at 3/24/19 4:26 PM: ---------------------------------------------------------------- You need to update the throttle secion of the {project}_manual template in `jobs/confs/yaml/templates/system_tests_templates.yaml` was (Author: dbelenky(a)redhat.com) You need to update the throttle secion of the '{project}_manual' template in `jobs/confs/yaml/templates/system_tests_templates.yaml` > Increase limits on concurrent https://jenkins.ovirt.org/job/standard-manual-runner/ jobs > ---------------------------------------------------------------------------------------- > > Key: OVIRT-2704 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2704 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > 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