- Infra - oVirt List Archives

[JIRA] (OVIRT-2078) Check option for private changes on Gerrit
by sbonazzo (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2078?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-2078: --------------------------------- User story: A researcher find a vulnerability in one of the oVirt packages. A CVE is opened and an embargo date is acknowledged between researcher, oVirt package maintainer and downstream vendors. Between report and embargo date, oVirt package maintainer must be able to push a patch to gerrit as a private patch, getting it reviewed by a restricted number of people and get it ready for being merged immediately on embargo lift, when the vulnerability will be disclosed to public, in order to issue an immediate release right after the merge. > Check option for private changes on Gerrit > ------------------------------------------ > > Key: OVIRT-2078 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2078 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri > Assignee: infra > Priority: High > > We need an option sometimes to post private changes ( not draft ) to Gerrit, > Gerrit has support for private changes [1], we should check if its available in current version. > [1] https://gerrit-review.googlesource.com/Documentation/intro-user.html#privat… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2074) missing dependency for python-isort
by sbonazzo (oVirt JIRA) 05 Jun '18

05 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2074?page=com.atlassian.jira.… ] sbonazzo reassigned OVIRT-2074: ------------------------------- Assignee: sbonazzo (was: infra) > missing dependency for python-isort > ----------------------------------- > > Key: OVIRT-2074 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2074 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: sbonazzo > Labels: cq-issue-traking, ost_failures > > need to change fc27 to fc28 to fix the failures. > Sandro submitted a change for some projects but some are still missing. > Sandro: > Fix is here: https://gerrit.ovirt.org/91769 ; needs an engine to be built on fedora to pass CI, I'm on it. > Going on failures, I will help him with the change for failed projects build-artifacts with the same issue. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: 91378, 3 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Jun '18

05 Jun '18

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

1 0

[CQ]: 91841, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 04 Jun '18

04 Jun '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 228 - Failure!
by jenkins＠jenkins.phx.ovirt.org 04 Jun '18

04 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/228/ Build Number: 228 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #228 [Milan Zamazal] Use Cirros 0.4.0 for cluster versions < 4.1 [Yuval Turgeman] system-tests: added he-node-ng-master suite [Barak Korren] Fix mock_cleanup.sh trying to umount bad things [Barak Korren] Switch fabric-ovirt to STDCI v2 ----------------- Failed Tests: ----------------- No tests ran.

1 3

[CQ]: 91888,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 04 Jun '18

04 Jun '18

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

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-master - Build # 446 - Failure!
by jenkins＠jenkins.phx.ovirt.org 04 Jun '18

04 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-master/446/ Build Number: 446 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #446 [Gal Ben Haim] 4.2: Backport tests from master [Barak Korren] Fix mock_cleanup.sh trying to umount bad things [Barak Korren] Switch fabric-ovirt to STDCI v2 ----------------- Failed Tests: ----------------- No tests ran.

1 3

[JIRA] (OVIRT-2134) Investigate why HC suites fail on slaves with *-IBRS CPU
by Gal Ben Haim (oVirt JIRA) 04 Jun '18

04 Jun '18

Gal Ben Haim created OVIRT-2134: ----------------------------------- Summary: Investigate why HC suites fail on slaves with *-IBRS CPU Key: OVIRT-2134 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2134 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Gal Ben Haim Assignee: infra The HC suites work just fine on "ovirt-srv05.phx.ovirt.org". while failing on "ovirt-srv21.phx.ovirt.org" and "ovirt-srv18.phx.ovirt.org". One thing that I've noticed is the difference between the CPU types on those slaves: ovirt-srv05.phx.ovirt.org - IvyBridge ovirt-srv21.phx.ovirt.org and ovirt-srv18.phx.ovirt.org - Haswell-noTSX-IBRS Together with [1], I have a strong feeling that this is the issue. [1] - https://gerrit.ovirt.org/#/c/90542/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2133) Explain how to remove a stale OST env
by Gal Ben Haim (oVirt JIRA) 04 Jun '18

04 Jun '18

Gal Ben Haim created OVIRT-2133: ----------------------------------- Summary: Explain how to remove a stale OST env Key: OVIRT-2133 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2133 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Gal Ben Haim Assignee: infra If the lago prefix was removed without calling `lago destroy`, stale networks and VMs can be still running on the host. If so, the following error might occur: {code:java} libvirtError: internal error: Network is already in use by interface SOME INTERFACE NAME {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-1933) Could not resolve host: mirrorlist.centos.org; Unknown error
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1933?page=com.atlassian.jira.… ] eyal edri updated OVIRT-1933: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > Could not resolve host: mirrorlist.centos.org; Unknown error > ------------------------------------------------------------ > > Key: OVIRT-1933 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1933 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Roy Golan > Assignee: infra > > I remember we had that in the past. And it looks intermittent. > http://jenkins.ovirt.org/blue/organizations/jenkins/rgolangh_ovirt-flexdriv… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0