Bug 1002189

Summary: qemu-sanity-check doesn't work with kernel-debug kernels
Product: [Fedora] Fedora Reporter: Richard W.M. Jones <rjones>
Component: qemu-sanity-checkAssignee: Richard W.M. Jones <rjones>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: rjones
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-sanity-check-1.1.4-2.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-28 15:34:51 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:
Bug Depends On:    
Bug Blocks: 999518    

Description Richard W.M. Jones 2013-08-28 15:17:21 UTC
Description of problem:

kernel-debug kernels have debugging information, but are
otherwise regular kernels.  qemu-sanity-check cannot use
these kernels because they have names like:

/boot/vmlinuz-3.11.0-0.rc7.git0.1.fc21.x86_64+debug

whereas qemu-sanity-check searches for kernels using this
wildcard:

/boot/vmlinuz-*.$arch

Although it's possible to work around this by using an
explicit --kernel parameter, it'd be nice if +debug
kernel were recognized.

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

qemu-sanity-check 1.1.3

Additional info:

https://bugzilla.redhat.com/show_bug.cgi?id=999518#c6

Comment 1 Richard W.M. Jones 2013-08-28 15:34:51 UTC
Fixed in 1.1.4.

http://koji.fedoraproject.org/koji/taskinfo?taskID=5865333

Comment 2 Fedora Update System 2013-08-28 16:15:58 UTC
qemu-sanity-check-1.1.4-2.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/qemu-sanity-check-1.1.4-2.fc19

Comment 3 Fedora Update System 2013-10-01 01:53:40 UTC
qemu-sanity-check-1.1.4-2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.