- Infra - oVirt List Archives

[JIRA] (OVIRT-2130) Support for private changes in Gerrit
by sbonazzo (oVirt JIRA) 04 Jun '18

04 Jun '18

sbonazzo created OVIRT-2130: ------------------------------- Summary: Support for private changes in Gerrit Key: OVIRT-2130 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2130 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra Hi, can you please upgrade gerrit to latest version so we can leverage support for private changes when working on security related patches? 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> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

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

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2108?page=com.atlassian.jira.… ] eyal edri moved OST-35 to OVIRT-2108: ------------------------------------- Project: oVirt - virtualization made easy (was: oVirt system tests) Workflow: Task Management Workflow (was: Software Simplified Workflow for Project OST) Key: OVIRT-2108 (was: OST-35) > 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 > Reporter: sbonazzo > Assignee: infra > Labels: ost_ticket_tmp > > 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#100086)

1 0

[JIRA] (OVIRT-2095) Re: he-basic-ansible_suite_master: failed to set MSR 0xd90 to 0x0
by eyal edri (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2095?page=com.atlassian.jira.… ] eyal edri moved OST-106 to OVIRT-2095: -------------------------------------- Project: oVirt - virtualization made easy (was: oVirt system tests) Workflow: Task Management Workflow (was: Software Simplified Workflow for Project OST) Key: OVIRT-2095 (was: OST-106) > Re: he-basic-ansible_suite_master: failed to set MSR 0xd90 to 0x0 > ----------------------------------------------------------------- > > Key: OVIRT-2095 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2095 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri > Assignee: Gal Ben Haim > Labels: ost_ticket_tmp > > Opening a ticket on it, Gal will look into it, it might take some time to > investigate. > On Mon, Mar 26, 2018 at 1:24 PM, Yedidyah Bar David <didi(a)redhat.com> wrote: > > Hi all, > > > > Trying to run ovirt-system-tests using mock_runner.sh on my laptop > > (i7-6820HQ T460p, RHEL 7.4, kernel 3.10.0-693.17.1.el7.x86_64, > > qemu-kvm-rhev-2.9.0-16.el7_4.13.x86_64). > > > > hosted-engine deploy starts, and fails while running virt-install to > > create the engine vm (which will be a nested-kvm vm). > > > > qemu log on the nested-kvm host0 says: > > > > 2018-03-26T08:02:16.727212Z qemu-kvm: error: failed to set MSR 0xd90 to 0x0 > > qemu-kvm: /builddir/build/BUILD/qemu-2.9.0/target/i386/kvm.c:1843: > > kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed. > > > > Searched and found this: > > > > https://bugs.launchpad.net/qemu/+bug/1665389 > > > > which seems very similar, although from a year ago and about a fedora > > 24 kernel+qemu. The conclusion there is: > > > > <quote> > > Yes, I mean '-cpu host' in the bare metal. There is no workaround; it > > worked by chance and it triggered other hard to find bugs. > > </quote> > > > > So, what should I/we do? Is there a workaround? How does this work > > elsewhere? > > > > Thanks, > > -- > > Didi > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > -- > Eyal edri > MANAGER > RHV DevOps > EMEA VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2092) standard-enqueue 4.2 not running
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2092?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2092: ------------------------------------- You linked to [91900|https://gerrit.ovirt.org/#/c/91900/] in this ticket, but the patch you actually re added according to the link you provided here is [91886|https://gerrit.ovirt.org/#/c/91886] You can see that change had gone into testing here: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-q… And that test finished successfully: https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2282/ The success was reported here: https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-q… Which is why the queue became empty. Non of this indicated any issue with standard enqueue. If you re-add a change by re-running the "add" build on the main CQ job - standard-enqueue is not even a part of the process. > standard-enqueue 4.2 not running > -------------------------------- > > Key: OVIRT-2092 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2092 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_infra > > I was looking to see if https://gerrit.ovirt.org/#/c/91900/ fixed the issues on the dwh alerts and I found that we re-added the change to cq this morning: > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > but the tested is showing that it only ran once (yesterday): > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > and "next test" job is showing empty queue: > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > seems like there is an issue in: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/standard-enqueue/14… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2092) standard-enqueue 4.2 not running
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2092?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2092: ------------------------------------- WRT [build 14051|https://jenkins.ovirt.org/view/Change queue jobs/job/standard-enqueue/14051] - its perfect;y fine. The 'jenkins' project does not build any RPMs so there is nothing to submit to any queues. > standard-enqueue 4.2 not running > -------------------------------- > > Key: OVIRT-2092 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2092 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_infra > > I was looking to see if https://gerrit.ovirt.org/#/c/91900/ fixed the issues on the dwh alerts and I found that we re-added the change to cq this morning: > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > but the tested is showing that it only ran once (yesterday): > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > and "next test" job is showing empty queue: > http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… > seems like there is an issue in: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/standard-enqueue/14… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2093) Add OST 4.2 -> 4.2 upgrade suit
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2093?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2093: ----------------------------------- Assignee: Daniel Belenky (was: infra) > Add OST 4.2 -> 4.2 upgrade suit > ------------------------------- > > Key: OVIRT-2093 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2093 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Barak Korren > Assignee: Daniel Belenky > Priority: High > > OST is currently missing a suit to properly test upgrades from 4.2 "released" to 4.2 "tested". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2093) Add OST 4.2 -> 4.2 upgrade suit
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

Barak Korren created OVIRT-2093: ----------------------------------- Summary: Add OST 4.2 -> 4.2 upgrade suit Key: OVIRT-2093 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2093 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Barak Korren Assignee: infra Priority: High OST is currently missing a suit to properly test upgrades from 4.2 "released" to 4.2 "tested". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2093) Add OST 4.2 -> 4.2 upgrade suit
by Barak Korren (oVirt JIRA) 04 Jun '18

04 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2093?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2093: -------------------------------- Epic Link: OVIRT-2091 > Add OST 4.2 -> 4.2 upgrade suit > ------------------------------- > > Key: OVIRT-2093 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2093 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Barak Korren > Assignee: infra > Priority: High > > OST is currently missing a suit to properly test upgrades from 4.2 "released" to 4.2 "tested". -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2092) standard-enqueue 4.2 not running
by Dafna Ron (oVirt JIRA) 04 Jun '18

04 Jun '18

Dafna Ron created OVIRT-2092: -------------------------------- Summary: standard-enqueue 4.2 not running Key: OVIRT-2092 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2092 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Priority: Highest I was looking to see if https://gerrit.ovirt.org/#/c/91900/ fixed the issues on the dwh alerts and I found that we re-added the change to cq this morning: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… but the tested is showing that it only ran once (yesterday): http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… and "next test" job is showing empty queue: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-4.2_change-qu… seems like there is an issue in: http://jenkins.ovirt.org/view/Change%20queue%20jobs/job/standard-enqueue/14… -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

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

04 Jun '18

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

1 0