May 2018 - Infra - Ovirt List Archives

[oVirt Jenkins] ovirt-appliance_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 49 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el... Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.2_build-artifacts-el... Build Number: 49 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #49 [Emil Natan] Add Emil's email alias to whitelist [Martin Perina] wildfly: wildfly-overlay: Add FC28 builds [Martin Perina] engine-extensions: Add FC28 builds [Barak Korren] Don't run check-patch-s390x.sh on merge [Evgheni Dereveanchin] Verify Jenkins user settings from global_setup [Yuval Turgeman] Revert "Test building with ansible25" ----------------- Failed Tests: ----------------- No tests ran.

7 years

1
1
0 / 0

[CQ]: 91524,2 (ovirt-provider-ovn) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 91524,2 (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/91524/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2016/

7 years

1
0
0 / 0

[CQ]: 91329, 4 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

7 years

1
0
0 / 0

[CQ]: 91524,2 (ovirt-provider-ovn) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 91524,2 (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/91524/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2014/

7 years

1
0
0 / 0

CVE-2018-3639 - Important - oVirt - Speculative Store Bypass

by Sandro Bonazzola

As you may have already heard, an industry-wide issue was found in the way many modern microprocessor designs have implemented speculative execution of Load & Store instructions. This issue is well described by CVE-2018-3639 announce available at https://access.redhat.com/security/cve/cve-2018-3639. oVirt team has released right now an update of ovirt-engine to version 4.2.3.7 which add support for SSBD CPUs in order to mitigate the security issue. If you are running oVirt on Red Hat Enterprise Linux, please apply updates described in https://access.redhat.com/security/cve/cve-2018-3639. If you are running oVirt on CentOS Linux please apply updated described by: CESA-2018:1629 Important CentOS 7 kernel Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022843.html> CESA-2018:1632 Important CentOS 7 libvirt Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022840.html> CESA-2018:1649 Important CentOS 7 java-1.8.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022839.html> CESA-2018:1648 Important CentOS 7 java-1.7.0-openjdk Security Update <https://lists.centos.org/pipermail/centos-announce/2018-May/022838.html> An update for qemu-kvm-ev has been also tagged for release and announced with CESA-2018:1655 Important: qemu-kvm-ev security update <https://lists.centos.org/pipermail/centos-virt/2018-May/005804.html> but due to some issues in CentOS release process for Virt SIG content, it is not yet available on mirrors. We are working with CentOS community to get the packages signed and published as soon as possible. In the meanwhile you can still get the update package by enabling the test repository https://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common/ on your systems or manually installing the package from the repository. If you're running oVirt on a different Linux distribution, please check with your vendor for available updates. Please note that to fully mitigate this vulnerability, system administrators must apply both hardware “microcode” updates and software patches that enable new functionality. At this time, microprocessor microcode will be delivered by the individual manufacturers. The oVirt team recommends end users and systems administrator to apply any available updates as soon as practical. Thanks, -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://red.ht/sig> <https://redhat.com/summit>

7 years

1
1
0 / 0

[CQ]: 91331, 1 (ovirt-host) failed "ovirt-4.2" system tests, but isn't the failure root cause

by oVirt Jenkins

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

7 years

1
0
0 / 0

[CQ]: 90951, 6 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

7 years

1
0
0 / 0

[oVirt Jenkins] ovirt-node-ng_ovirt-4.2_build-artifacts-el7-x86_64 - Build # 284 - Failure!

by jenkins＠jenkins.phx.ovirt.org

Project: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-... Build: http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-4.2_build-artifacts-el7-... Build Number: 284 Build Status: Failure Triggered By: Started by user Sandro Bonazzola ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #284 [Sandro Bonazzola] kickstart: drop upstream cockpit copr repo ----------------- Failed Tests: ----------------- No tests ran.

7 years

1
1
0 / 0

[JIRA] (OVIRT-2054) false change reported since package is not deployed on ost

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2054?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2054: ------------------------------------- {quote} Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? {quote} If its being used you will see in installed in the 'deploy' phase, or by engins-setup or during AddHost. The interesting thing here is why did the CQ test fail if the patch is not being actually tested. > false change reported since package is not deployed on ost > ---------------------------------------------------------- > > Key: OVIRT-2054 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > The package is not deployed on OST so it could not have been the reason for failure. > + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report. > Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

7 years

1
0
0 / 0

[CQ]: 91042, 8 (vdsm) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

7 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra May 2018