RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1578483 - Failing qemu-iotests x86_64 rhev
Summary: Failing qemu-iotests x86_64 rhev
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.6
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ademar Reis
QA Contact: Tingting Mao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-15 16:56 UTC by Lukáš Doktor
Modified: 2019-03-18 21:08 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-18 21:08:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Avocado results of qemu-iotests. In "version" you can see the qemu/kernel version and the "qemu-iotests" contains qemu-iotests from the execution. (1.30 MB, application/x-bzip)
2018-05-15 16:56 UTC, Lukáš Doktor 		no flags Details
View All

Description Lukáš Doktor 2018-05-15 16:56:26 UTC 
Created attachment 1436855 [details]
Avocado results of qemu-iotests. In "version" you can see the qemu/kernel version and the "qemu-iotests" contains qemu-iotests from the execution.

Description of problem:
There are many failing qemu-iotests, let's track them here.

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.12.0-1.el7.x86_64
How reproducible:
Always (with some fluctuation)

Steps to Reproduce:
1. Install qemu-kvm-rhev
2. Checkout the installed version git repo
3. ./configure
4. cd tests/qemu-iotests
5. ./check $TESTNAME_INCLUDING_ARGS

Actual results:
not ok 3 -nbd -raw 001;run-7449
not ok 4 -nbd -qcow2 001;run-7449
not ok 7 -nbd -raw 002;run-7449
not ok 8 -nbd -qcow2 002;run-7449
not ok 11 -nbd -raw 003;run-7449
not ok 12 -nbd -qcow2 003;run-7449
not ok 15 -nbd -raw 004;run-7449
not ok 16 -nbd -qcow2 004;run-7449
not ok 19 -nbd -raw 005;run-7449
not ok 20 -nbd -qcow2 005;run-7449
not ok 24 -nbd -qcow2 007;run-7449
not ok 27 -nbd -raw 008;run-7449
not ok 28 -nbd -qcow2 008;run-7449
not ok 31 -nbd -raw 009;run-7449
not ok 32 -nbd -qcow2 009;run-7449
not ok 35 -nbd -raw 010;run-7449
not ok 36 -nbd -qcow2 010;run-7449
not ok 39 -nbd -raw 011;run-7449
not ok 40 -nbd -qcow2 011;run-7449
not ok 56 -nbd -qcow2 015;run-7449
not ok 60 -nbd -qcow2 017;run-7449
not ok 75 -nbd -raw 021;run-7449
not ok 76 -nbd -qcow2 021;run-7449
not ok 80 -nbd -qcow2 022;run-7449
not ok 100 -nbd -qcow2 027;run-7449
not ok 108 -nbd -qcow2 029;run-7449
not ok 110 -file -qcow2 030;run-7449
not ok 112 -nbd -qcow2 030;run-7449
not ok 119 -nbd -raw 032;run-7449
not ok 120 -nbd -qcow2 032;run-7449
not ok 123 -nbd -raw 033;run-7449
not ok 124 -nbd -qcow2 033;run-7449
not ok 132 -nbd -qcow2 035;run-7449
not ok 154 -file -qcow2 041;run-7449
not ok 156 -nbd -qcow2 041;run-7449
not ok 169 -file -raw 045;run-7449
not ok 171 -nbd -raw 045;run-7449
not ok 180 -nbd -qcow2 047;run-7449
not ok 194 -file -qcow2 051;run-7449
not ok 209 -file -raw 055;run-7449
not ok 210 -file -qcow2 055;run-7449
not ok 211 -nbd -raw 055;run-7449
not ok 212 -nbd -qcow2 055;run-7449
not ok 240 -nbd -qcow2 062;run-7449
not ok 256 -nbd -qcow2 066;run-7449
not ok 264 -nbd -qcow2 068;run-7449
not ok 284 -nbd -qcow2 073;run-7449
not ok 299 -nbd -raw 077;run-7449
not ok 313 -file -raw 081;run-7449
not ok 324 -nbd -qcow2 083;run-7449
not ok 361 -file -raw 093;run-7449
not ok 363 -nbd -raw 093;run-7449
not ok 367 -nbd -raw 094;run-7449
not ok 368 -nbd -qcow2 094;run-7449
not ok 403 -nbd -raw 104;run-7449
not ok 404 -nbd -qcow2 104;run-7449
not ok 408 -nbd -qcow2 105;run-7449
not ok 444 -nbd -qcow2 114;run-7449
not ok 446 -file -qcow2 115;run-7449
not ok 457 -file -raw 118;run-7449
not ok 458 -file -qcow2 118;run-7449
not ok 459 -nbd -raw 118;run-7449
not ok 460 -nbd -qcow2 118;run-7449
not ok 463 -nbd -raw 119;run-7449
not ok 474 -file -qcow2 122;run-7449
not ok 479 -nbd -raw 123;run-7449
not ok 508 -nbd -qcow2 130;run-7449
not ok 524 -nbd -qcow2 134;run-7449
not ok 529 -file -raw 136;run-7449
not ok 531 -nbd -raw 136;run-7449
not ok 538 -file -qcow2 138;run-7449
not ok 542 -file -qcow2 139;run-7449
not ok 544 -nbd -qcow2 139;run-7449
not ok 567 -nbd -raw 145;run-7449
not ok 568 -nbd -qcow2 145;run-7449
not ok 573 -file -raw 147;run-7449
not ok 574 -file -qcow2 147;run-7449
not ok 575 -nbd -raw 147;run-7449
not ok 576 -nbd -qcow2 147;run-7449
not ok 577 -file -raw 148;run-7449
not ok 579 -nbd -raw 148;run-7449
not ok 608 -nbd -qcow2 156;run-7449
not ok 616 -nbd -qcow2 158;run-7449
not ok 650 -file -qcow2 172;run-7449
not ok 660 -nbd -qcow2 174;run-7449
not ok 683 -nbd -raw 181;run-7449
not ok 684 -nbd -qcow2 181;run-7449
not ok 693 -file -raw 184;run-7449
not ok 694 -file -qcow2 184;run-7449
not ok 695 -nbd -raw 184;run-7449
not ok 696 -nbd -qcow2 184;run-7449
not ok 702 -file -qcow2 186;run-7449
not ok 712 -nbd -qcow2 188;run-7449
not ok 716 -nbd -qcow2 189;run-7449
not ok 741 -file -raw 197;run-7449
not ok 742 -file -qcow2 197;run-7449
not ok 743 -nbd -raw 197;run-7449
not ok 744 -nbd -qcow2 197;run-7449
not ok 748 -nbd -qcow2 198;run-7449
not ok 760 -nbd -qcow2 201;run-7449
not ok 809 -vmdk 059;run-7449
not ok 815 -vdi 084;run-7449

Expected results:
all should PASS (or be skipped)

Additional info:
Tests were executed via Avocado, results are attached, but it's reproducible directly by "./check $testname" where testname is in format "not ok \d+ ([^;]+);.*" (basically there is "not ok" string, followed by serial id which you should ignore as well as everything after the last ";". So the last "not ok 733 -vmdk 059;run-7449" => "./check -vdi 084")
Comment 2 Lukáš Doktor 2018-05-15 17:09:08 UTC 
Note there were some left-behind processes after the execution, usually test 077 and some nbd processes. Repeating the execution usually increases the number of failed tests.

I also created similar reports for other architectures and you can see the differences by running "avocado diff $RESULTS1 $RESULTS2". The other BZs are:

* https://bugzilla.redhat.com/show_bug.cgi?id=1578473
* https://bugzilla.redhat.com/show_bug.cgi?id=1578477
* https://bugzilla.redhat.com/show_bug.cgi?id=1578479
* https://bugzilla.redhat.com/show_bug.cgi?id=1578481
Comment 3 Ping Li 2018-05-16 02:38:55 UTC 
(In reply to Lukas Doktor from comment #0)
> Created attachment 1436855 [details]
> Avocado results of qemu-iotests. In "version" you can see the qemu/kernel
> version and the "qemu-iotests" contains qemu-iotests from the execution.
> 
> Description of problem:
> There are many failing qemu-iotests, let's track them here.
> 
> Version-Release number of selected component (if applicable):
> qemu-kvm-rhev-2.12.0-1.el7.x86_64
> How reproducible:
> Always (with some fluctuation)
> 
> Steps to Reproduce:
> 1. Install qemu-kvm-rhev
> 2. Checkout the installed version git repo
> 3. ./configure
> 4. cd tests/qemu-iotests
> 5. ./check $TESTNAME_INCLUDING_ARGS
> 
> Actual results:
> not ok 3 -nbd -raw 001;run-7449
> not ok 4 -nbd -qcow2 001;run-7449
> not ok 7 -nbd -raw 002;run-7449
> not ok 8 -nbd -qcow2 002;run-7449
> not ok 11 -nbd -raw 003;run-7449
> not ok 12 -nbd -qcow2 003;run-7449
> not ok 15 -nbd -raw 004;run-7449
> not ok 16 -nbd -qcow2 004;run-7449
> not ok 19 -nbd -raw 005;run-7449
> not ok 20 -nbd -qcow2 005;run-7449
> not ok 24 -nbd -qcow2 007;run-7449
> not ok 27 -nbd -raw 008;run-7449
> not ok 28 -nbd -qcow2 008;run-7449
> not ok 31 -nbd -raw 009;run-7449
> not ok 32 -nbd -qcow2 009;run-7449
> not ok 35 -nbd -raw 010;run-7449
> not ok 36 -nbd -qcow2 010;run-7449
> not ok 39 -nbd -raw 011;run-7449
> not ok 40 -nbd -qcow2 011;run-7449
> not ok 56 -nbd -qcow2 015;run-7449
> not ok 60 -nbd -qcow2 017;run-7449
> not ok 75 -nbd -raw 021;run-7449
> not ok 76 -nbd -qcow2 021;run-7449
> not ok 80 -nbd -qcow2 022;run-7449
> not ok 100 -nbd -qcow2 027;run-7449
> not ok 108 -nbd -qcow2 029;run-7449
> not ok 110 -file -qcow2 030;run-7449
> not ok 112 -nbd -qcow2 030;run-7449
> not ok 119 -nbd -raw 032;run-7449
> not ok 120 -nbd -qcow2 032;run-7449
> not ok 123 -nbd -raw 033;run-7449
> not ok 124 -nbd -qcow2 033;run-7449
> not ok 132 -nbd -qcow2 035;run-7449
> not ok 154 -file -qcow2 041;run-7449
> not ok 156 -nbd -qcow2 041;run-7449
> not ok 169 -file -raw 045;run-7449
> not ok 171 -nbd -raw 045;run-7449
> not ok 180 -nbd -qcow2 047;run-7449
> not ok 194 -file -qcow2 051;run-7449
> not ok 209 -file -raw 055;run-7449
> not ok 210 -file -qcow2 055;run-7449
> not ok 211 -nbd -raw 055;run-7449
> not ok 212 -nbd -qcow2 055;run-7449
> not ok 240 -nbd -qcow2 062;run-7449
> not ok 256 -nbd -qcow2 066;run-7449
> not ok 264 -nbd -qcow2 068;run-7449
> not ok 284 -nbd -qcow2 073;run-7449
> not ok 299 -nbd -raw 077;run-7449
> not ok 313 -file -raw 081;run-7449
> not ok 324 -nbd -qcow2 083;run-7449
> not ok 361 -file -raw 093;run-7449
> not ok 363 -nbd -raw 093;run-7449
> not ok 367 -nbd -raw 094;run-7449
> not ok 368 -nbd -qcow2 094;run-7449
> not ok 403 -nbd -raw 104;run-7449
> not ok 404 -nbd -qcow2 104;run-7449
> not ok 408 -nbd -qcow2 105;run-7449
> not ok 444 -nbd -qcow2 114;run-7449
> not ok 446 -file -qcow2 115;run-7449
> not ok 457 -file -raw 118;run-7449
> not ok 458 -file -qcow2 118;run-7449
> not ok 459 -nbd -raw 118;run-7449
> not ok 460 -nbd -qcow2 118;run-7449
> not ok 463 -nbd -raw 119;run-7449
> not ok 474 -file -qcow2 122;run-7449
> not ok 479 -nbd -raw 123;run-7449
> not ok 508 -nbd -qcow2 130;run-7449
> not ok 524 -nbd -qcow2 134;run-7449
> not ok 529 -file -raw 136;run-7449
> not ok 531 -nbd -raw 136;run-7449
> not ok 538 -file -qcow2 138;run-7449
> not ok 542 -file -qcow2 139;run-7449
> not ok 544 -nbd -qcow2 139;run-7449
> not ok 567 -nbd -raw 145;run-7449
> not ok 568 -nbd -qcow2 145;run-7449
> not ok 573 -file -raw 147;run-7449
> not ok 574 -file -qcow2 147;run-7449
> not ok 575 -nbd -raw 147;run-7449
> not ok 576 -nbd -qcow2 147;run-7449
> not ok 577 -file -raw 148;run-7449
> not ok 579 -nbd -raw 148;run-7449
> not ok 608 -nbd -qcow2 156;run-7449
> not ok 616 -nbd -qcow2 158;run-7449
> not ok 650 -file -qcow2 172;run-7449
> not ok 660 -nbd -qcow2 174;run-7449
> not ok 683 -nbd -raw 181;run-7449
> not ok 684 -nbd -qcow2 181;run-7449
> not ok 693 -file -raw 184;run-7449
> not ok 694 -file -qcow2 184;run-7449
> not ok 695 -nbd -raw 184;run-7449
> not ok 696 -nbd -qcow2 184;run-7449
> not ok 702 -file -qcow2 186;run-7449
> not ok 712 -nbd -qcow2 188;run-7449
> not ok 716 -nbd -qcow2 189;run-7449
> not ok 741 -file -raw 197;run-7449
> not ok 742 -file -qcow2 197;run-7449
> not ok 743 -nbd -raw 197;run-7449
> not ok 744 -nbd -qcow2 197;run-7449
> not ok 748 -nbd -qcow2 198;run-7449
What does '-nbd -qcow2' mean? Run qcow2 on nbd backend?

> not ok 760 -nbd -qcow2 201;run-7449
> not ok 809 -vmdk 059;run-7449
> not ok 815 -vdi 084;run-7449
> 
> Expected results:
> all should PASS (or be skipped)
> 
> Additional info:
> Tests were executed via Avocado, results are attached, but it's reproducible
> directly by "./check $testname" where testname is in format "not ok \d+
> ([^;]+);.*" (basically there is "not ok" string, followed by serial id which
> you should ignore as well as everything after the last ";". So the last "not
> ok 733 -vmdk 059;run-7449" => "./check -vdi 084")
Should be ./check -vmdk 059 ?

There are two bugs(bug 1331279 and bug 1537485) to track qemu-iotests failures for qcow2/raw/vmdk/vhdx/luks on local backend.
Comment 4 Lukáš Doktor 2018-05-16 16:36:56 UTC 
> > not ok 744 -nbd -qcow2 197;run-7449
> > not ok 748 -nbd -qcow2 198;run-7449
> What does '-nbd -qcow2' mean? Run qcow2 on nbd backend?
> 

Yep. Basically it's an equivalent of running "./check -nbd -qcow2 198".

> > not ok 760 -nbd -qcow2 201;run-7449
> > not ok 809 -vmdk 059;run-7449
> > not ok 815 -vdi 084;run-7449
> > 
> > Expected results:
> > all should PASS (or be skipped)
> > 
> > Additional info:
> > Tests were executed via Avocado, results are attached, but it's reproducible
> > directly by "./check $testname" where testname is in format "not ok \d+
> > ([^;]+);.*" (basically there is "not ok" string, followed by serial id which
> > you should ignore as well as everything after the last ";". So the last "not
> > ok 733 -vmdk 059;run-7449" => "./check -vdi 084")
> Should be ./check -vmdk 059 ?
> 

Yep, sorry for the typo.

> There are two bugs(bug 1331279 and bug 1537485) to track qemu-iotests
> failures for qcow2/raw/vmdk/vhdx/luks on local backend.

Good to know. The reason they are included here is that I run these in my CI because the last couple of tests require specific setting and are not covered by the 4 main scenarios I test so I run them "extra". I also lack the "nfs" one as that one is completely broken (reported directly to Alex few months back...)
Comment 6 Ademar Reis 2019-03-18 21:08:39 UTC 
Our downstream CI team is now running qemu-iotests. Several of them are even enabled in %check as part of rpmbuild.

The ones that are broken in the CI or brew environment are being reported in bugzilla (there are several reported already).

So I'm closing all of the old qemu-iotest BZs. We'll work on them in this more controlled environment of CI and brew.
Note You need to log in before you can comment on or make changes to this bug.