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

Bug 874715

Summary: fv_ tests fail to mount data image after guest run
Product: [Retired] Red Hat Hardware Certification Program Reporter: Greg Nichols <gnichols>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED ERRATA QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.6.4CC: bbrock, czhang, jbrier, rlandry
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-01 18:20:04 UTC Type: Bug
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 test patch to wait and retry if loop device isn't ready none

Description Greg Nichols 2012-11-08 17:48:46 UTC 
Description of problem:

The fv_ tests can fail to mount the data image after the guest test run.  Example log:

Guest files verified
Unmounting /mnt
Using loopback device /dev/loop0 for guest data image
add map loop0p1 (253:3): 0 192717 linear /dev/loop0 63
Error: could not mount data image
"ls /dev/mapper" no match for regular expression loop0p[0-9]
...Done: return value = 1.


Version-Release number of selected component (if applicable):

v7 1.6.4 R8
RHEL 6.4
Comment 1 Greg Nichols 2012-11-08 17:50:39 UTC 
The problem appears to be that the loop device is not ready when v7 attempts to use it, running "ls /dev/mapper" to find the name of the new device.
Comment 2 John Brier 2012-11-08 22:16:34 UTC 
Greg, I ran into another issue on RHEL6.4-20121106.0 with kdump being affected by an LVM2 change. I got some help debugging it and I wonder if it could be the cause of this issue too.. could be a long shot though bug 874832
Comment 3 John Brier 2012-11-09 16:30:07 UTC 
(In reply to comment #2)
> Greg, I ran into another issue on RHEL6.4-20121106.0 with kdump being
> affected by an LVM2 change. I got some help debugging it and I wonder if it
> could be the cause of this issue too.. could be a long shot though bug 874832

It seems my educated guess was right. I tried the workaround from bug 874832:

edit lvm.conf to include:

verify_udev_operations = 1

and now it works 

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
v7 image: host: v7-1.5-32, guest: v7-1.5-32  build:  2012-06-01 23:32:39
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/loop0p1    92M  6.7M   80M   8% /mnt
total 1192
drwxr-xr-x.  3 root root   1024 Nov  9 11:25 .
dr-xr-xr-x. 23 root root   4096 Nov  8 16:43 ..
drwx------.  2 root root  12288 Jun  9  2009 lost+found
-rw-r--r--.  1 root root 724680 Nov  9 11:25 results.xml
-rw-r--r--.  1 root root 464836 Jun  1 19:28 v7-1.5-32.el5.noarch.rpm
-rwxr--r--.  1 root root    228 Nov  9 11:13 v7-guest-script
-rw-r--r--.  1 root root    269 Jun  1 19:34 v7-image.xml
core Passed
Comment 4 Greg Nichols 2012-11-12 13:47:11 UTC 
Created attachment 643536 [details]
fv test patch to wait and retry if loop device isn't ready
Comment 9 errata-xmlrpc 2013-02-01 18:20:04 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.

http://rhn.redhat.com/errata/RHBA-2013-0222.html