June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2054) false change reported since package is not deployed on ost
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2054?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2054: ---------------------------------- I did not keep the original build. will leave open until we see this again. > 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, ost_race > > 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#100087)

1 0

[JIRA] (OVIRT-2148) 005_network_by_label.assign_hosts_network_label
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2148?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2148: ----------------------------- Issue Type: Bug (was: Task) > 005_network_by_label.assign_hosts_network_label > ------------------------------------------------ > > Key: OVIRT-2148 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2148 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > Change 91614,10 (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/91614/10 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2312/ > Fault reason is "Operation Failed". Fault detail is "[Cannot add Label. Another Setup Networks or Host Refresh process in progress on the host. Please try later.]". HTTP response code is 409. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2022) libguestfs-1.36.10-6.el7.centos.ppc64le requires qemu-img-ma
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2022?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2022: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > libguestfs-1.36.10-6.el7.centos.ppc64le requires qemu-img-ma > ------------------------------------------------------------- > > Key: OVIRT-2022 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2022 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra, ost_infra_packages > > build-artifacts failing on http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/3508/c… > The error is package missing for; > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Error: Package: 1:libguestfs-1.36.10-6.el7.centos.ppc64le (el) > 12:20:11 Requires: qemu-img-ma > 12:20:11 Available: 10:qemu-img-ma-2.10.0-21.el7.ppc64le (el) > 12:20:11 qemu-img-ma = 10:2.10.0-21.el7 > 12:20:11 Available: 10:qemu-img-ma-2.10.0-21.el7_5.1.ppc64le (el-updates) > 12:20:11 qemu-img-ma = 10:2.10.0-21.el7_5.1 > 12:20:11 You could try using --skip-broken to work around the problem > 12:20:11 You could try running: rpm -Va --nofiles --nodigest > 12:20:11 > 12:20:11 Init took 28 seconds > 12:20:11 ============================ > 12:20:11 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > 12:20:11 @@ Thu May 10 12:20:11 UTC 2018 automation/build-artifacts.sh chroot finished > 12:20:11 @@ took 28 seconds > 12:20:11 @@ rc = 1 > 12:20:11 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > 12:20:11 ========== Scrubbing chroot > 12:20:11 mock \ > The issue is with centos: > https://bugzilla.redhat.com/show_bug.cgi?id=1570533 > The 7.5.1 should come out tomorrow and this issue will be fixed > opening ticket to follow up and make sure that its back to normal tomorrow. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2022) libguestfs-1.36.10-6.el7.centos.ppc64le requires qemu-img-ma
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2022?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2022: ---------------------------------- this indeed is resolved. closing > libguestfs-1.36.10-6.el7.centos.ppc64le requires qemu-img-ma > ------------------------------------------------------------- > > Key: OVIRT-2022 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2022 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra, ost_infra_packages > > build-artifacts failing on http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-el7-ppc64le/3508/c… > The error is package missing for; > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Package qemu-img-ma is obsoleted by qemu-img-ev, but obsoleting package does not provide for requirements > 12:20:11 Error: Package: 1:libguestfs-1.36.10-6.el7.centos.ppc64le (el) > 12:20:11 Requires: qemu-img-ma > 12:20:11 Available: 10:qemu-img-ma-2.10.0-21.el7.ppc64le (el) > 12:20:11 qemu-img-ma = 10:2.10.0-21.el7 > 12:20:11 Available: 10:qemu-img-ma-2.10.0-21.el7_5.1.ppc64le (el-updates) > 12:20:11 qemu-img-ma = 10:2.10.0-21.el7_5.1 > 12:20:11 You could try using --skip-broken to work around the problem > 12:20:11 You could try running: rpm -Va --nofiles --nodigest > 12:20:11 > 12:20:11 Init took 28 seconds > 12:20:11 ============================ > 12:20:11 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > 12:20:11 @@ Thu May 10 12:20:11 UTC 2018 automation/build-artifacts.sh chroot finished > 12:20:11 @@ took 28 seconds > 12:20:11 @@ rc = 1 > 12:20:11 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > 12:20:11 ========== Scrubbing chroot > 12:20:11 mock \ > The issue is with centos: > https://bugzilla.redhat.com/show_bug.cgi?id=1570533 > The 7.5.1 should come out tomorrow and this issue will be fixed > opening ticket to follow up and make sure that its back to normal tomorrow. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2027) NPE with no thread appears in engine log
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2027?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2027: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) > NPE with no thread appears in engine log > ---------------------------------------- > > Key: OVIRT-2027 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2027 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > This is not failing tests but should be fixed > [CQ]: 84817,6 (ovirt-engine) failed "ovirt-master" system tests > For further details about the change see: > https://gerrit.ovirt.org/#/c/84817/6 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7601/ > 2018-05-16 03:10:00,001-04 ERROR [org.ovirt.engine.core.bll.AutoRecoveryManager] (EE-ManagedThreadFactory-engineScheduled-Thread-92) [] Exception in recover: NullPointerException: -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2027) NPE with no thread appears in engine log
by Dafna Ron (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2027?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2027: ---------------------------------- I looked in several builds with failures and could not find this. I am closing as cannot reproduce. > NPE with no thread appears in engine log > ---------------------------------------- > > Key: OVIRT-2027 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2027 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures > > This is not failing tests but should be fixed > [CQ]: 84817,6 (ovirt-engine) failed "ovirt-master" system tests > For further details about the change see: > https://gerrit.ovirt.org/#/c/84817/6 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7601/ > 2018-05-16 03:10:00,001-04 ERROR [org.ovirt.engine.core.bll.AutoRecoveryManager] (EE-ManagedThreadFactory-engineScheduled-Thread-92) [] Exception in recover: NullPointerException: -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

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

12 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/253/ Build Number: 253 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #253 [Marcin Mirecki] network: add test validating connections between OVN networks ----------------- Failed Tests: ----------------- No tests ran.

1 1

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

12 Jun '18

A system test invoked by the "ovirt-master" change queue including change 92070,4 (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/92070/4 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/8166/

1 0

[JIRA] (OVIRT-2108) Enable ovirt-system-tests for ppc64le
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2108?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2108: ----------------------------- Epic Link: (was: OVIRT-400) > Enable ovirt-system-tests for ppc64le > ------------------------------------- > > Key: OVIRT-2108 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2108 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: sbonazzo > Assignee: infra > > We're using ppc64le hosts in oVirt CI infrastructure under oVirt management. > It's our own production system so I think it would be valuable to have system tests running also with ppc64le hosts, not only x86_64. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2108) Enable ovirt-system-tests for ppc64le
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2108?page=com.atlassian.jira.… ] eyal edri updated OVIRT-2108: ----------------------------- Epic Link: (was: OVIRT-400) > Enable ovirt-system-tests for ppc64le > ------------------------------------- > > Key: OVIRT-2108 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2108 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: OST > Reporter: sbonazzo > Assignee: infra > > We're using ppc64le hosts in oVirt CI infrastructure under oVirt management. > It's our own production system so I think it would be valuable to have system tests running also with ppc64le hosts, not only x86_64. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0