February 2019 - Infra - Ovirt List Archives

[CQ]: 98097, 1 (ovirt-release) failed "ovirt-4.3" system tests, but isn't the failure root cause

by oVirt Jenkins

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

5 years, 9 months

1
0
0 / 0

[CQ]: 98099, 1 (ovirt-node-ng-image) failed "ovirt-4.3" system tests, but isn't the failure root cause

by oVirt Jenkins

A system test invoked by the "ovirt-4.3" change queue including change 98099,1 (ovirt-node-ng-image) failed. However, this change seems not to be the root cause for this failure. Change 97519,2 (ovirt-node-ng-image) 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 97519,2 (ovirt-node-ng-image) 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/98099/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/97519/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/93/

5 years, 9 months

1
0
0 / 0

[CQ]: 98096,1 (ovirt-release) failed "ovirt-4.3" system tests

by oVirt Jenkins

Change 98096,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/98096/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/91/

5 years, 9 months

1
0
0 / 0

[CQ]: 98098,1 (ovirt-appliance) failed "ovirt-4.3" system tests

by oVirt Jenkins

Change 98098,1 (ovirt-appliance) 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/98098/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/89/

5 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-2688) OST manual: enable engine 4.3

by Anton Marchukov (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2688?page=com.atlassian.jir... ] Anton Marchukov commented on OVIRT-2688: ---------------------------------------- Most of 4.3 suites are already prepared, we are making sure they are working and then we will enable 4.3 selector. -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat > OST manual: enable engine 4.3 > ----------------------------- > > Key: OVIRT-2688 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2688 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Attachments: Screenshot from 2019-02-27 21-52-28.png > > > When starting manual OST job, we can select engine version. > The available options are: > - master > - 42 > Since we have now 4.3 branch, we should be able to select 4.3 engine. > See attached screenshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

5 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-2688) OST manual: enable engine 4.3

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2688?page=com.atlassian.jir... ] Eyal Edri commented on OVIRT-2688: ---------------------------------- Its also pending when/if the 4.3 suites are ready and working, I think they are still WIP. On Thu, Feb 28, 2019 at 9:50 AM Yedidyah Bar David <didi(a)redhat.com> wrote: > On Wed, Feb 27, 2019 at 9:56 PM Nir Soffer <nsoffer(a)redhat.com> wrote: > > > > When starting manual OST job, we can select engine version. > > The available options are: > > - master > > - 42 > > > > Since we have now 4.3 branch, we should be able to select 4.3 engine. > > We didn't branch yet. Tal should branch it RSN. > -- > Didi > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/2R7NEKEVL3M... > -- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > OST manual: enable engine 4.3 > ----------------------------- > > Key: OVIRT-2688 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2688 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > Attachments: Screenshot from 2019-02-27 21-52-28.png > > > When starting manual OST job, we can select engine version. > The available options are: > - master > - 42 > Since we have now 4.3 branch, we should be able to select 4.3 engine. > See attached screenshot. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

5 years, 9 months

2
1
0 / 0

OST manual: enable engine 4.3

by Nir Soffer

When starting manual OST job, we can select engine version. The available options are: - master - 42 Since we have now 4.3 branch, we should be able to select 4.3 engine. See attached screenshot.

5 years, 9 months

3
2
0 / 0

How to run manual job with standard STDCIV2 build results?

by Yedidyah Bar David

Hi all, I run [1] and it fails with [2]: 2019-02-27 08:27:00,821::log_utils.py::__enter__::600::ovirtlago.reposetup::INFO:: # Running repoman: [0m [0m 2019-02-27 08:27:00,822::log_utils.py::__enter__::600::lago.utils::DEBUG::start task:87982007-be04-4d4b-af19-751f85f8df25:Run command: "repoman" "--option=main.on_empty_source=warn" "--option=store.RPMStore.on_wrong_distro=copy_to_all" "--option=store.RPMStore.with_srcrpms=false" "--option=store.RPMStore.with_sources=false" "--option=store.RPMStore.rpm_dir=" "/dev/shm/ost/deployment-upgrade-from-release-suite-master/default/internal_repo/default" "add" "conf:/home/jenkins/workspace/ovirt-system-tests_manual/ovirt-system-tests/upgrade-from-release-suite-master/extra_sources" "/var/lib/lago/ovirt-master-tested-el7:only-missing" "/var/lib/lago/ovirt-master-snapshot-static-el7:only-missing" "/var/lib/lago/glusterfs-5-el7:only-missing" "/var/lib/lago/centos-updates-el7:only-missing" "/var/lib/lago/centos-base-el7:only-missing" "/var/lib/lago/centos-extras-el7:only-missing" "/var/lib/lago/epel-el7:only-missing" "/var/lib/lago/centos-ovirt-4.3-el7:only-missing" "/var/lib/lago/centos-ovirt-common-el7:only-missing" "/var/lib/lago/centos-qemu-ev-testing-el7:only-missing" "/var/lib/lago/centos-opstools-testing-el7:only-missing" "/var/lib/lago/centos-sclo-rh-release-el7:only-missing": 2019-02-27 08:28:08,161::utils.py::_run_command::192::lago.utils::DEBUG::87982007-be04-4d4b-af19-751f85f8df25: command exit with return code: 1 2019-02-27 08:28:08,161::utils.py::_run_command::197::lago.utils::DEBUG::87982007-be04-4d4b-af19-751f85f8df25: command stderr: 2019-02-27 08:27:01,014::INFO::repoman.cmd:: 2019-02-27 08:27:01,014::INFO::repoman.cmd::Adding artifacts to the repo /dev/shm/ost/deployment-upgrade-from-release-suite-master/default/internal_repo/default 2019-02-27 08:27:01,015::INFO::repoman.common.stores.RPM::Loading repo /dev/shm/ost/deployment-upgrade-from-release-suite-master/default/internal_repo/default 2019-02-27 08:27:01,015::INFO::repoman.common.stores.RPM::Repo /dev/shm/ost/deployment-upgrade-from-release-suite-master/default/internal_repo/default loaded 2019-02-27 08:27:01,015::INFO::repoman.common.stores.iso::Loading repo /dev/shm/ost/deployment-upgrade-from-release-suite-master/default/internal_repo/default 2019-02-27 08:27:01,016::INFO::repoman.common.stores.iso::Repo /dev/shm/ost/deployment-upgrade-from-release-suite-master/default/internal_repo/default loaded 2019-02-27 08:27:01,020::INFO::repoman.common.repo::Resolving artifact source rec:https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1007... 2019-02-27 08:27:01,022::INFO::repoman.common.sources.url::Recursively fetching URL (level 0): https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1007/art... 2019-02-27 08:28:08,127::ERROR::repoman.cmd::maximum recursion depth exceeded in cmp Perhaps this is a bug, or a result of supplying in CUSTOM_REPOS [3]: rec:https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1007... Is this a bug? If not, what's the correct way to supply a subtree of the exported artifacts of some (standard CI) build? Thanks, [1] https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... [2] https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-te... [3] https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1007/art... -- Didi

5 years, 9 months

3
4
0 / 0

oVirt infra daily report - unstable production jobs - 749

by jenkins＠jenkins.phx.ovirt.org

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/749//artifact/exported... Cheers, Jenkins

5 years, 9 months

1
0
0 / 0

[CQ]: 98015,6 (vdsm) failed "ovirt-master" system tests

by oVirt Jenkins

Change 98015,6 (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/98015/6 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13175/

5 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra February 2019