Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 663901

Summary: v7: fv_storage testing destroy the swap partition of fv_image
Product: [Retired] Red Hat Hardware Certification Program Reporter: chen yuwen <yuchen>
Component: Test Suite (distribution)Assignee: Greg Nichols <gnichols>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: low    
Version: 1.2CC: czhang, rlandry, sdenham
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-01 14:45:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
fv_storage destroy swap none

Description chen yuwen 2010-12-17 09:24:44 UTC
Created attachment 469320 [details]
fv_storage destroy swap

Description of problem:
fv_storage testing destroy the swap partition of fv_image, and then fv_storage and the following fv_tests which need swap can not swapon and fail.

Version-Release number of selected component (if applicable):
OS: RHEL5.6-Server-20101208.1
Arch: x86_64, i386, ia64
Virtualization: kvm(x86_64), hvm(x86_64, i386, ia64)

How reproducible:
100%

Steps to Reproduce:
1. find a system supporting kvm or hvm.
2. install RHEL5.6 and packages v7.
3. run fv_storage testing : "v7 run -t fv_storage", and run "virsh console v7$arch" to monitor the guest.
4. run other fv_tests and monitor the guest.
  
Actual results:
FAIL by lack of swap space.

Expected results:
PASS

Additional info:
Happen on RHEL5, RHEL6.

Comment 1 Rob Landry 2011-01-05 15:27:11 UTC
The storage test should restore swap when it is completed I thought?

Which combinations does this occur with as we're not getting this report from in the field and I would expect it to impact all FV certs?

Comment 2 chen yuwen 2011-01-06 07:35:21 UTC
*** Bug 662913 has been marked as a duplicate of this bug. ***

Comment 6 chen yuwen 2011-01-10 06:11:54 UTC
Pass on v7data-20110107.img.tar.bz2.

#v7 run -t fv_storage
...
FV Guest started ...
fv_storage test is running, it takes some time(less than 60 minutes), please be patient ...
You may use "virsh console v7x86_64" to monitor the testing progress
Guest has shutdown
Using loopback device /dev/loop0 for guest data image
add map loop0p1 (253:3): 0 192717 linear /dev/loop0 63
Mounted /dev/mapper/loop0p1 on /mnt
storage Passed
Unmounting /mnt
Deleting loopback device /dev/loop0 configuration.
del devmap : loop0p1
...finished running ./fv_storage.py, exit code=0
...

#virsh console v7x86_64
...
*** Testing raw I/O performance on mapper/VolGroup00-LogVol01
Warning: can not get device size from /sys/block/mapper/VolGroup00-LogVol01/size, defaulting to 1048576. 
--- sequential write
...

Comment 8 Greg Nichols 2011-01-10 14:34:01 UTC
New image pushed to Partner's, and the symbolic link is updated.