June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2162) docs: Only explain how to run OST inside mock
by Gal Ben Haim (oVirt JIRA) 10 Jun '18

10 Jun '18

Gal Ben Haim created OVIRT-2162: ----------------------------------- Summary: docs: Only explain how to run OST inside mock Key: OVIRT-2162 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2162 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Gal Ben Haim Assignee: infra We prefer to use mock when running OST, because then we can install the engine SDK from the internal repo (inside mock we use the root user). Currently, the docs contains an explanation on how to run with/without mock, which makes the docs complicated. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2161) Adjust run_suite to a manual trigger inside mock
by Gal Ben Haim (oVirt JIRA) 10 Jun '18

10 Jun '18

Gal Ben Haim created OVIRT-2161: ----------------------------------- Summary: Adjust run_suite to a manual trigger inside mock Key: OVIRT-2161 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2161 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Gal Ben Haim Assignee: infra We need to make run_suite do the following: - Add the `KVM` device if it's missing - Install engine SDK on the host. Currently, `suite.sh` is handling those tasks. The problem is that `suite.sh` sets a trap which calls cleanup on exit, which isn't always desired when running locally. * The implementation shouldn't assume that the root user invoked `run_suite` because there are still some people who prefer not to use mock when running OST. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[CQ]: d00d8ca (stage-gh-stdci2) failed "dummy-master" system tests
by oVirt Jenkins 10 Jun '18

10 Jun '18

Change d00d8ca (stage-gh-stdci2) is probably the reason behind recent system test failures in the "dummy-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://github.com/oVirt/stage-gh-stdci2/commit/d00d8cac105f7be15d2a0559522… For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/176/

1 0

[CQ]: 05e7f07 (ovirt-ansible-manageiq) failed "ovirt-master" system tests
by oVirt Jenkins 10 Jun '18

10 Jun '18

Change 05e7f07 (ovirt-ansible-manageiq) 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://github.com/oVirt/ovirt-ansible-manageiq/commit/05e7f07da9285b9904fb… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8147/

1 0

[CQ]: 05e7f07 (ovirt-ansible-manageiq) failed "ovirt-4.2" system tests
by oVirt Jenkins 10 Jun '18

10 Jun '18

Change 05e7f07 (ovirt-ansible-manageiq) 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://github.com/oVirt/ovirt-ansible-manageiq/commit/05e7f07da9285b9904fb… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2359/

1 0

[CQ]: d00d8ca (stage-gh-stdci2) failed "dummy-master" system tests
by oVirt Jenkins 10 Jun '18

10 Jun '18

Change d00d8ca (stage-gh-stdci2) is probably the reason behind recent system test failures in the "dummy-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://github.com/oVirt/stage-gh-stdci2/commit/d00d8cac105f7be15d2a0559522… For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/172/

1 0

[JIRA] (OVIRT-2153) Fedora 28 ppc64le support
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2153?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2153: ------------------------------------- We never supported building on PPC64LE for anything other then EL7. We can add support if it is desired, but since we managed without Fedora so far, do we really want to add support for it now? > 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

ovirt-ansible-disaster-recovery build jobs not triggered
by Sandro Bonazzola 10 Jun '18

10 Jun '18

https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-disaster-recovery_standar… shows no build job triggered. Can you please fix it? 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>

2 2

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

10 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/463/ Build Number: 463 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #463 [Sandro Bonazzola] hc-basic-suite-master: fix otopi package listing ----------------- Failed Tests: ----------------- No tests ran.

1 3

[JIRA] (OVIRT-2159) ovirt-ansible-manageiq build jobs not triggered
by Daniel Belenky (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2159?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-2159: --------------------------------------- See my comment from OVIRT-2160. It's the same issue: the PR was merged to 1.1.10. This branch is not being tracked by STDCI (not mapped to any queue in autoamtion.yaml) > ovirt-ansible-manageiq build jobs not triggered > ----------------------------------------------- > > Key: OVIRT-2159 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2159 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_build-arifacts, ost_failures, ost_infra > > https://jenkins.ovirt.org/job/oVirt_ovirt-ansible-manageiq_standard-on-ghpu… > shows no build job triggered. Can you please fix it? > Thanks, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0