ovirt-engine cq failing on test 098_ovirt_provider_ovn.use_ovn_provider - libvirtError: 'queues' attribute must be positive number:

Description

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/

Activity

Show:

Dafna Ron July 4, 2018 at 12:31 PM

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?

Former user July 2, 2018 at 1:05 PM

Issue has been fixed, mail was sent by me and Daniel about this issue.
here is a link to CQ that passed with all the changes:
https://jenkins.ovirt.org/view/Change%20queue%20jobs/job/ovirt-master_change-queue/25958/

Barak Korren July 1, 2018 at 6:20 AM

If you think https://gerrit.ovirt.org/#/c/92567/ is not the cause of this issue, why is CQ pointing to it? did it fail on a another issue you also have to report?

Fixed

Details

Assignee

Reporter

Priority

Created June 28, 2018 at 9:18 AM
Updated September 2, 2018 at 3:50 PM
Resolved July 4, 2018 at 1:03 PM

Flag notifications