- Infra - oVirt List Archives

[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

[JIRA] (OVIRT-686) Find a better way to show unstable status in CI
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-686?page=com.atlassian.jira.p… ] eyal edri updated OVIRT-686: ---------------------------- Epic Link: (was: OVIRT-400) > Find a better way to show unstable status in CI > ----------------------------------------------- > > Key: OVIRT-686 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-686 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, monitoring > Reporter: eyal edri > Assignee: infra > Priority: Low > > Today we have the main view on jenkins.ovirt.org showing the unstable list of jobs, > While its effective in showing the current stable jobs, its not optimal in showing trends, history or dashboard view of the jenkins itself. > We need to find a jenkins plugin or a dashboard to show the current status of Jenkins in a more efficient and informative way. > There are numerous dashboards and view plugins, just need to find the right one for oVirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-686) Find a better way to show unstable status in CI
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-686?page=com.atlassian.jira.p… ] eyal edri updated OVIRT-686: ---------------------------- Epic Link: (was: OVIRT-400) > Find a better way to show unstable status in CI > ----------------------------------------------- > > Key: OVIRT-686 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-686 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, monitoring > Reporter: eyal edri > Assignee: infra > Priority: Low > > Today we have the main view on jenkins.ovirt.org showing the unstable list of jobs, > While its effective in showing the current stable jobs, its not optimal in showing trends, history or dashboard view of the jenkins itself. > We need to find a jenkins plugin or a dashboard to show the current status of Jenkins in a more efficient and informative way. > There are numerous dashboards and view plugins, just need to find the right one for oVirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2153) Fedora 28 ppc64le support
by sbonazzo (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2153?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-2153: --------------------------------- we want to expand testing for future updates, so I think having ppc64le support would be beneficial to the project. > Fedora 28 ppc64le support > ------------------------- > > Key: OVIRT-2153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2153 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: sbonazzo > Assignee: infra > > Hi, > I see python-ovirt-engine-sdk4 failing on ppc64le for fc28 due to: "Unable > to find mock env" error. > I tend to think we should have ppc64le for fedora 28 but I see that mock > config are missing in jenkins and also the mirroring of the repos for > fedora 28 ppc64le are missing. > We should either drop ppc64le jobs for fc28 or add support for it. Adding > Ondra to share his thoughts on this. > -- > 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-686) Find a better way to show unstable status in CI
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-686?page=com.atlassian.jira.p… ] eyal edri updated OVIRT-686: ---------------------------- Component/s: monitoring Jenkins Master > Find a better way to show unstable status in CI > ----------------------------------------------- > > Key: OVIRT-686 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-686 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, monitoring > Reporter: eyal edri > Assignee: infra > Priority: Low > > Today we have the main view on jenkins.ovirt.org showing the unstable list of jobs, > While its effective in showing the current stable jobs, its not optimal in showing trends, history or dashboard view of the jenkins itself. > We need to find a jenkins plugin or a dashboard to show the current status of Jenkins in a more efficient and informative way. > There are numerous dashboards and view plugins, just need to find the right one for oVirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2191) remove the mountpoint creation phase from mock_runner
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2191?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2191: -------------------------------- Assignee: Barak Korren (was: infra) Status: In Progress (was: To Do) > remove the mountpoint creation phase from mock_runner > ----------------------------------------------------- > > Key: OVIRT-2191 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2191 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: Barak Korren > > There is a part in mock_runner code that runs mock in order to create mount points for things that are going to be bind mounted into it. Since mock 1.4.10 can create its own mount point we can remove that code from mock runner. > This should reduce the amount of times mock is called from mock_runner -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0