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 1427176 - test cases of qemu-iotests failed
Summary: test cases of qemu-iotests failed
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Hanna Czenczek
QA Contact: Ping Li
URL:
Whiteboard:
: 1170963 (view as bug list)
Depends On:
Blocks: 1431530 1436473
TreeView+ depends on / blocked
 
Reported: 2017-02-27 14:17 UTC by Ping Li
Modified: 2018-03-22 03:23 UTC (History)
17 users (show)

Fixed In Version: qemu-kvm-1.5.3-134.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 17:46:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
log for qcow2 test on rhel7.4 (57.56 KB, text/plain)
2017-02-27 14:18 UTC, Ping Li 		no flags Details
log for qcow2 test on rhel7.4 after applied patch (75.16 KB, text/plain)
2017-03-11 04:33 UTC, Ping Li 		no flags Details
log for vmdk test on rhel7.4 after applied patch (10.58 KB, text/plain)
2017-03-11 04:34 UTC, Ping Li 		no flags Details
log for vhdx test on rhel7.4 after applied patch (11.43 KB, text/plain)
2017-03-11 04:34 UTC, Ping Li 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1856 0 normal SHIPPED_LIVE Moderate: qemu-kvm security, bug fix, and enhancement update 2017-08-01 18:03:36 UTC

Description Ping Li 2017-02-27 14:17:55 UTC 
Description of problem:
test cases 026 030 049 086 and 095 of qemu-iotests failed for qcow2. The issue also can be reproduced on rhel7.3z with below packages:
qemu-kvm-1.5.3-126.el7_3.5
kernel-3.10.0-514.10.2.el7

Version-Release number of selected component (if applicable):
qemu-kvm-1.5.3-132.el7
kernel-3.10.0-576.el7

How reproducible:
2/2

Steps to Reproduce:
1.#brew download-build --rpm qemu-kvm-1.5.3-132.el7.src.rpm
2.#rpm -ivhf qemu-kvm-1.5.3-132.el7.src.rpm && rpmbuild -bp /root/rpmbuild/SPECS/qemu-kvm.spec --nodeps --force
3.#cd /root/rpmbuild/BUILD/qemu-1.5.3/tests/qemu-iotests
4.#export QEMU_PROG=/usr/libexec/qemu-kvm
5.#./check -qcow2

Actual results:


Expected results:
All case passed except not run

Additional info:
Comment 2 Ping Li 2017-02-27 14:18:39 UTC 
Created attachment 1258110 [details]
log for qcow2 test on rhel7.4
Comment 3 Hanna Czenczek 2017-03-08 20:31:22 UTC 
Hi,

The test results posted in comment 2 don't seem to match the result from the original description (different tests are failing). Also, I am not sure which tests you are running exactly. Are those the upstream tests or the ones that are in RHEL's downstream qemu-kvm repository?

I'm asking because so far I only see 026 and 030 failing and I cannot see test 095 downstream.

Also, you have to make sure that not only QEMU_PROG is set but also QEMU_IMG_PROG (to qemu-img), QEMU_IO_PROG (to qemu-io), and QEMU_NBD_PROG (to qemu-nbd). The log from comment 2 looks like it's using the standard system versions of qemu-img and qemu-io there, and I'm not sure whether those are in the same version as the qemu you are trying to test.


Max
Comment 7 Ping Li 2017-03-11 04:33:32 UTC 
Created attachment 1262105 [details]
log for qcow2 test on rhel7.4 after applied patch
Comment 8 Ping Li 2017-03-11 04:34:07 UTC 
Created attachment 1262106 [details]
log for vmdk test on rhel7.4 after applied patch
Comment 9 Ping Li 2017-03-11 04:34:37 UTC 
Created attachment 1262107 [details]
log for vhdx test on rhel7.4 after applied patch
Comment 10 Hanna Czenczek 2017-03-13 00:56:20 UTC 
Thanks! Now I'm able to reproduce all of the qcow2 failures and working on fixing them.

Most of the vmdk and vhdx failures however are due to missing test images. Those are present in the git repository, just not in the source RPM. Since vmdk and vhdx are not exactly vital, I'd say that if you want to test them anyway you would have to use the git repository instead of the SRPM as the basis for testing.

If that does not fit into the test cycle very well, I think it would be fine to just omit vmdk and vhdx from testing (or anything that is not qcow2 or raw for that matter).

Max
Comment 11 Kevin Wolf 2017-03-14 16:21:39 UTC 
*** Bug 1170963 has been marked as a duplicate of this bug. ***
Comment 12 Hanna Czenczek 2017-03-16 00:26:33 UTC 
Stefan made me reconsider my opinion from comment 10 that we could just omit vmdk and vhdx from testing. So if you need to run the tests from the SRPM and cannot run them from the git repository (or at least pull the test images from the repository), we will have to put the sample images into the SRPM as well.

So, would it be possible for you to run the tests from the repository instead of from the SRPM?

Max
Comment 14 Miroslav Rezanina 2017-03-21 14:20:49 UTC 
Fix included in qemu-kvm-1.5.3-134.el7
Comment 17 Ping Li 2017-03-23 07:29:57 UTC 
Verify the issue with below packages and steps, all the cases for qcow2, raw, vhdx and vmdk are passed when run the test suit from the repository.

package version:
qemu-kvm-1.5.3-134.el7
kernel-3.10.0-619.el7

steps:
1. #git clone git://git.app.eng.bos.redhat.com/virt/rhel7/qemu-kvm.git
2. #cd /home/qemu-kvm
3. #git checkout qemu-kvm-1.5.3-134.el7
4. #cd tests/qemu-iotests
5. #export QEMU_PROG=/usr/libexec/qemu-kvm
6. #./check -qcow2(raw/vhdx/vmdk)

test results:
qcow2: Passed all 69 tests
raw: Passed all 20 tests
vhdx: Passed all 17 tests
vmdk: Passed all 26 tests
Comment 18 Ping Li 2017-03-23 07:41:34 UTC 
Hi Max,

Could you help to check the comment 13? Thanks in advance.

When ran the test suit from SRPM, the failure can still be reproduced.
vhdx:
Failures: 064 070
vmdk:
Failures: 059
Comment 19 Hanna Czenczek 2017-03-27 14:16:56 UTC 
Hi pingl,

Yes, as I wrote, those fail because the required sample images are missing from the SRPM. Miroslav Rezanina has told me that this will be no longer be an issue in 7.5, but for 7.4 we would require a specific fix (and just for 7.4).

So I'm not sure how to continue with this bug. From my point of view the most important fixes are merged now. Maybe Miroslav will write a patch to include the sample images in the SRPM; or I guess we can just keep the bug open until 7.5 but I'm not sure whether our process likes a bug that is neither NEW/ASSIGNED nor CLOSED to move from one release to another.

I have asked Miroslav to write such a patch if he thinks it's worth the effort so that we don't have to move this BZ to 7.5.


Max
Comment 20 Ping Li 2017-03-27 14:46:58 UTC 
(In reply to Max Reitz from comment #19)
> Hi pingl,
> 
> Yes, as I wrote, those fail because the required sample images are missing
> from the SRPM. Miroslav Rezanina has told me that this will be no longer be
> an issue in 7.5, but for 7.4 we would require a specific fix (and just for
> 7.4).
> 
> So I'm not sure how to continue with this bug. From my point of view the
> most important fixes are merged now. Maybe Miroslav will write a patch to
> include the sample images in the SRPM; or I guess we can just keep the bug
> open until 7.5 but I'm not sure whether our process likes a bug that is
> neither NEW/ASSIGNED nor CLOSED to move from one release to another.
> 
> I have asked Miroslav to write such a patch if he thinks it's worth the
> effort so that we don't have to move this BZ to 7.5.
> 
> 
> Max

Hi Max,

Many thanks for your info. I opened a new bug 1436280 to track the missing sample images, then we can set this bug as verified according to the comment 17.
Thanks again for your help.
Comment 22 errata-xmlrpc 2017-08-01 17:46:48 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:1856
Note You need to log in before you can comment on or make changes to this bug.