- Infra - oVirt List Archives

[CQ]: 98096,1 (ovirt-release) failed "ovirt-4.3" system tests
by oVirt Jenkins 28 Feb '19

28 Feb '19

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/

1 0

[CQ]: 98098,1 (ovirt-appliance) failed "ovirt-4.3" system tests
by oVirt Jenkins 28 Feb '19

28 Feb '19

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/

1 0

[JIRA] (OVIRT-2688) OST manual: enable engine 4.3
by Anton Marchukov (oVirt JIRA) 28 Feb '19

28 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2688?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-2688) OST manual: enable engine 4.3
by Eyal Edri (oVirt JIRA) 28 Feb '19

28 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2688?page=com.atlassian.jira.… ] 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/2R7NEKEVL3MEV… > -- 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)

2 1

OST manual: enable engine 4.3
by Nir Soffer 28 Feb '19

28 Feb '19

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.

3 2

How to run manual job with standard STDCIV2 build results?
by Yedidyah Bar David 28 Feb '19

28 Feb '19

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/a… 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/artif… 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/a… 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-test… [2] https://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt-system-test… [3] https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/1007/artif… -- Didi

3 4

oVirt infra daily report - unstable production jobs - 749
by jenkins＠jenkins.phx.ovirt.org 28 Feb '19

28 Feb '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/749//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 98015,6 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

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/

1 0

[JIRA] (OVIRT-2688) OST manual: enable engine 4.3
by Nir Soffer (oVirt JIRA) 27 Feb '19

27 Feb '19

Nir Soffer created OVIRT-2688: --------------------------------- Summary: 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 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)

1 0

[CQ]: 98087, 1 (ovirt-engine-nodejs-modules) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 27 Feb '19

27 Feb '19

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

1 0

[CQ]: 97485, 9 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

Change 97485,9 (ovirt-provider-ovn) 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/97485/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13168/

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 27 Feb '19

27 Feb '19

Failed to run project_setup.sh for: #1423 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-6qcbv.

1 0

[CQ]: 97485,9 (ovirt-provider-ovn) failed "ovirt-4.2" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

Change 97485,9 (ovirt-provider-ovn) 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/97485/9 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3953/

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 27 Feb '19

27 Feb '19

Failed to run project_setup.sh for: #1421 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-lxhwg.

1 0

[CQ]: 92805,4 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

Change 92805,4 (ovirt-engine-sdk) 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/92805/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13163/

1 0

Tracking creation of 4.3 branch
by Dafna Ron 27 Feb '19

27 Feb '19

Hi, I created a google sheet so we can track which projects created the 4.3 branch and also which ones have already added the branch to 4.3 CQ in CI [1] Can everyone please go through the sheet and mark the progress there + assign a contact for the project for doing this work? [1] https://docs.google.com/spreadsheets/d/1i142cTN_0QwOvogtlQiF6bcIYxTpBqYBed2… thanks! Dafna

2 4

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 27 Feb '19

27 Feb '19

Failed to run project_setup.sh for: #1416 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-75vnn.

1 3

[CQ]: 92805,4 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

Change 92805,4 (ovirt-engine-sdk) 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/92805/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13161/

1 0

[CQ]: 92805,4 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

Change 92805,4 (ovirt-engine-sdk) 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/92805/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13159/

2 2

[JIRA] (OVIRT-2687) Please add Carlos Rodrigues to CI whitelist
by Dafna Ron (oVirt JIRA) 27 Feb '19

27 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2687?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2687: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Please add Carlos Rodrigues to CI whitelist > ------------------------------------------- > > Key: OVIRT-2687 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2687 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ondra Machacek > Assignee: infra > > Hi, > please add Carlos Rodrigues (cmar(a)eurotux.com) to ovirt-engine-sdk CI whitelist. > Thanks, > Ondra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2687) Please add Carlos Rodrigues to CI whitelist
by Dafna Ron (oVirt JIRA) 27 Feb '19

27 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2687?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2687: ---------------------------------- thanks. we can close this as I can see the patch managed to trigger the build after adding to list; https://gerrit.ovirt.org/#/c/92805/ > Please add Carlos Rodrigues to CI whitelist > ------------------------------------------- > > Key: OVIRT-2687 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2687 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ondra Machacek > Assignee: infra > > Hi, > please add Carlos Rodrigues (cmar(a)eurotux.com) to ovirt-engine-sdk CI whitelist. > Thanks, > Ondra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2687) Please add Carlos Rodrigues to CI whitelist
by Eyal Edri (oVirt JIRA) 27 Feb '19

27 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2687?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2687: ---------------------------------- merged On Wed, Feb 27, 2019, 12:48 Dafna Ron (oVirt JIRA) < > Please add Carlos Rodrigues to CI whitelist > ------------------------------------------- > > Key: OVIRT-2687 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2687 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ondra Machacek > Assignee: infra > > Hi, > please add Carlos Rodrigues (cmar(a)eurotux.com) to ovirt-engine-sdk CI whitelist. > Thanks, > Ondra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2687) Please add Carlos Rodrigues to CI whitelist
by Dafna Ron (oVirt JIRA) 27 Feb '19

27 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2687?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2687: ---------------------------------- patch added - https://gerrit.ovirt.org/#/c/98083/ > Please add Carlos Rodrigues to CI whitelist > ------------------------------------------- > > Key: OVIRT-2687 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2687 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Ondra Machacek > Assignee: infra > > Hi, > please add Carlos Rodrigues (cmar(a)eurotux.com) to ovirt-engine-sdk CI whitelist. > Thanks, > Ondra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

2 1

[JIRA] (OVIRT-2687) Please add Carlos Rodrigues to CI whitelist
by Ondra Machacek (oVirt JIRA) 27 Feb '19

27 Feb '19

Ondra Machacek created OVIRT-2687: ------------------------------------- Summary: Please add Carlos Rodrigues to CI whitelist Key: OVIRT-2687 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2687 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Ondra Machacek Assignee: infra Hi, please add Carlos Rodrigues (cmar(a)eurotux.com) to ovirt-engine-sdk CI whitelist. Thanks, Ondra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2686) CQ vdsm are failing on server ovirt-srv23.phx.ovirt.org with the same error
by Dafna Ron (oVirt JIRA) 27 Feb '19

27 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2686?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-2686: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > CQ vdsm are failing on server ovirt-srv23.phx.ovirt.org with the same error > --------------------------------------------------------------------------- > > Key: OVIRT-2686 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2686 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Galit Rosenthal > Assignee: Evgheni Dereveanchin > > For example: > https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2686) CQ vdsm are failing on server ovirt-srv23.phx.ovirt.org with the same error
by Galit Rosenthal (oVirt JIRA) 27 Feb '19

27 Feb '19

Galit Rosenthal created OVIRT-2686: -------------------------------------- Summary: CQ vdsm are failing on server ovirt-srv23.phx.ovirt.org with the same error Key: OVIRT-2686 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2686 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Galit Rosenthal Assignee: infra For example: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_chang… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[CQ]: 97841,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

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

4 5

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 27 Feb '19

27 Feb '19

Failed to run project_setup.sh for: #1414 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-frslf.

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 27 Feb '19

27 Feb '19

Failed to run project_setup.sh for: #1414 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-dn8sg.

1 0

Space problem on mail server
by Marc Dequènes (Duck) 27 Feb '19

27 Feb '19

Quack, I'm just back from event and vacation and I barely scratched the top of my inbox but I saw postmaster 26 messages about lack of space. I'm taking care of it now and will need to shutdown the VM a short time to rework storage and partitioning. We have a MX2 so it should only create a small delay to receive ML messages. \_o<

2 2

[CQ]: 97976,19 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

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

1 0

[CQ]: 92805,4 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 27 Feb '19

27 Feb '19

Change 92805,4 (ovirt-engine-sdk) 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/92805/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13152/

1 0

oVirt infra daily report - unstable production jobs - 748
by jenkins＠jenkins.phx.ovirt.org 27 Feb '19

27 Feb '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/748//artifact/exported-a… Cheers, Jenkins

1 0

[CQ]: 97976,19 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 26 Feb '19

26 Feb '19

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

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 Feb '19

26 Feb '19

Failed to run project_setup.sh for: #1405 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-cb7nh.

1 0

[CQ]: 92805,4 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 26 Feb '19

26 Feb '19

Change 92805,4 (ovirt-engine-sdk) 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/92805/4 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13148/

1 0

[CQ]: 98026,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 26 Feb '19

26 Feb '19

Change 98026,3 (ovirt-engine) 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/98026/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/13144/

1 0

[JIRA] (OVIRT-2685) Email not found on mailing list
by Bitbucket (oVirt JIRA) 26 Feb '19

26 Feb '19

Bitbucket created OVIRT-2685: -------------------------------- Summary: Email not found on mailing list Key: OVIRT-2685 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2685 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Bitbucket Assignee: infra Hi, I'm trying to do a password reset on mailling list, it says email is not found. I'm receiving mailing list daily on al(a)cyberversion.com -- Robin -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JENKINS] Failed to setup proejct kubevirt_containerized-data-importer_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 26 Feb '19

26 Feb '19

Failed to run project_setup.sh for: #1403 containerized-data-importer [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-lpdpc.

1 0

[CQ]: 97841,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 26 Feb '19

26 Feb '19

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

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Anton Marchukov closed OVIRT-2662. ---------------------------------- Makes sense. Closing > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > 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#100098)

1 0

[JIRA] (OVIRT-2658) Error when fetching upstream sources
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2658?page=com.atlassian.jira.… ] Anton Marchukov updated OVIRT-2658: ----------------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > Error when fetching upstream sources > ------------------------------------ > > Key: OVIRT-2658 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2658 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > Please see my check patch > https://jenkins.ovirt.org/job/ovirt-engine-metrics_standard-check-patch/123… > Can you please check what is the issue? > Also, I still did not get a nightly patch for the upstream sources updates. > Thanks, > -- > 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#100098)

1 0

[JIRA] (OVIRT-2502) official releases not being tested by change queue
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2502?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2502: -------------------------------------- Assignee: Dafna Ron (was: infra) > official releases not being tested by change queue > -------------------------------------------------- > > Key: OVIRT-2502 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2502 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Dafna Ron > > Hi, > just noticed in > https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-q… > that both the patch including the official release patch and the > post-release patch has been added to the same change queue job, causing the > official release to be skipped in favor of the post release: > - Started by upstream project ovirt-4.2_change-queue > <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue/> build number 8642 > <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue/8642/> > originally caused by: > - Started by upstream project standard-enqueue > <https://jenkins.ovirt.org/job/standard-enqueue/> build number 16477 > <https://jenkins.ovirt.org/job/standard-enqueue/16477/> > originally caused by: > - Triggered by Gerrit: https://gerrit.ovirt.org/94367 > Other triggered builds for this event. > ovirt-engine_4.2_build-artifacts-el7-x86_64 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-el7-x86_64/> > #828 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-el7-x86_64/8…> > ovirt-engine_4.2_check-merged-el7-x86_64 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_check-merged-el7-x86_64/> > #800 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_check-merged-el7-x86_64/800/> > - Started by upstream project ovirt-4.2_change-queue > <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue/> build number 8643 > <https://jenkins.ovirt.org/job/ovirt-4.2_change-queue/8643/> > originally caused by: > - Started by upstream project standard-enqueue > <https://jenkins.ovirt.org/job/standard-enqueue/> build number 16478 > <https://jenkins.ovirt.org/job/standard-enqueue/16478/> > originally caused by: > - Triggered by Gerrit: https://gerrit.ovirt.org/94368 > Other triggered builds for this event. > ovirt-engine_4.2_build-artifacts-el7-x86_64 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-el7-x86_64/> > #829 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_build-artifacts-el7-x86_64/8…> > ovirt-engine_4.2_check-merged-el7-x86_64 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_check-merged-el7-x86_64/> > #801 > <https://jenkins.ovirt.org/job/ovirt-engine_4.2_check-merged-el7-x86_64/801/> > This is really bad, meaning that a regression introduced in the release > patch may be completely ignored provided that the post release patch fixes > it. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> > <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f…> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2658) Error when fetching upstream sources
by Shirly Radco (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2658?page=com.atlassian.jira.… ] Shirly Radco commented on OVIRT-2658: ------------------------------------- On Tue, Feb 26, 2019, 14:14 Anton Marchukov (oVirt JIRA) < Yes > Error when fetching upstream sources > ------------------------------------ > > Key: OVIRT-2658 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2658 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > Please see my check patch > https://jenkins.ovirt.org/job/ovirt-engine-metrics_standard-check-patch/123… > Can you please check what is the issue? > Also, I still did not get a nightly patch for the upstream sources updates. > Thanks, > -- > 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#100098)

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Eyal Edri (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2662: ---------------------------------- I think it can be closed. The bot also mentioned that a user can be added to the oVirt org or the project if we want to add him permenantly for whitelisting. > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > 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#100098)

1 0

[JIRA] (OVIRT-2625) lists.ovirt.org not showing threads
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2625?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2625: -------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > lists.ovirt.org not showing threads > ----------------------------------- > > Key: OVIRT-2625 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2625 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: Marc Dequènes (Duck) > Attachments: Selection_258.png > > > Hi, > lists.ovirt.org hyperkitty is once again not showing threads. I tried to > find my old Jira ticket, but Jira is down. > For example, this doesn't show the thread, but there are 8 replies: > https://lists.ovirt.org/archives/list/users@ovirt.org/thread/SDDH2OC5RBOVYY… > Screenshot: https://imgur.com/a/xHKDN6K > [image: Selection_258.png] > -- > 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#100098)

1 0

[JIRA] (OVIRT-2639) Add support to upstream sources to be able to test github PR
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2639?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2639: -------------------------------------- Assignee: Daniel Belenky (was: infra) > 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: Daniel Belenky > > 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#100098)

1 0

[JIRA] (OVIRT-2652) Supporting comments on ovirt-site Blog section
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2652?page=com.atlassian.jira.… ] Anton Marchukov reassigned OVIRT-2652: -------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > Supporting comments on ovirt-site Blog section > ---------------------------------------------- > > Key: OVIRT-2652 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2652 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roy Golan > Assignee: Marc Dequènes (Duck) > > It would be very useful to have a comment section on our ovirt site. > It is quite standard to have that on every blog out there, and for a reason > - you get > feedback and conversation around the topic, without going somewhere else > (users list, irc, etc...) > What do we need to do to help the middle man with that? > Regards, > Roy -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JIRA] (OVIRT-2658) Error when fetching upstream sources
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2658?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2658: ---------------------------------------- [~sradco(a)redhat.com] this looks to be temporary issues and I see the job is passing now. Are you ok with closing this? > Error when fetching upstream sources > ------------------------------------ > > Key: OVIRT-2658 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2658 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Shirly Radco > Assignee: infra > > Hi, > Please see my check patch > https://jenkins.ovirt.org/job/ovirt-engine-metrics_standard-check-patch/123… > Can you please check what is the issue? > Also, I still did not get a nightly patch for the upstream sources updates. > Thanks, > -- > 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#100098)

1 0

[JIRA] (OVIRT-2662) jenkins whitelist issue in ovirt-web-ui
by Anton Marchukov (oVirt JIRA) 26 Feb '19

26 Feb '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2662?page=com.atlassian.jira.… ] Anton Marchukov commented on OVIRT-2662: ---------------------------------------- [~bkorren(a)redhat.com] are you currently handling it or somebody else have to? I see this is in progress but no owner. > jenkins whitelist issue in ovirt-web-ui > --------------------------------------- > > Key: OVIRT-2662 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2662 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Greg Sheremeta > Assignee: infra > > Please see > https://github.com/oVirt/ovirt-web-ui/pull/931#issuecomment-457248843 > "As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors." The bot is lying -- > I have 'add to whitelist' for Bohdan several times now. > How do we cure this? > -- > 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#100098)

1 0