[ https://ovirt-jira.atlassian.net/browse/OVIRT-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37351#comment-37351 ] Dafna Ron commented on OVIRT-2265: ---------------------------------- [~bkorren@redhat.com] change marked as root cause and the actual root cause were in the same batch of tested changes. The cause of failure would effect this change as well however, without this change you cannot deploy ovn so the test would fail. it would be with different errors thought but I don't think that cq can differentiate between different errors right?
ovirt-engine cq failing on test 098_ovirt_provider_ovn.use_ovn_provider - libvirtError: 'queues' attribute must be positive number: ------------------------------------------------------------------------------------------------------------------------------------
Key: OVIRT-2265 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2265 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Priority: Highest Labels: cq-issue-traking, ost_code_regression, ost_failures
The change reported as responsible for the failure was a package change patch but I can see that some patches merged by Alona are more related to the issue. mail sent to list. Although CQ is pointing to this change: https://gerrit.ovirt.org/#/c/92567/ - packaging: Add python-netaddr requirement I actually think from the error its because of changes made to multiqueues https://gerrit.ovirt.org/#/c/92009/ - engine: Update libvirtVmXml to consider vmBase.multiQueuesEnabled attribute https://gerrit.ovirt.org/#/c/92008/ - engine: Introduce algorithm for calculating how many queues asign per vnic https://gerrit.ovirt.org/#/c/92007/ - engine: Add multiQueuesEnabled to VmBase https://gerrit.ovirt.org/#/c/92318/ - restapi: Add 'Multi Queues Enabled' to the relevant mappers https://gerrit.ovirt.org/#/c/92149/ - webadmin: Add 'Multi Queues Enabled' to vm dialog Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/
-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)