Bug 212193 - Bogus message on wrong device
Summary: Bogus message on wrong device
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xen
Version: 5.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Rik van Riel
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-25 16:00 UTC by Glauber Costa
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version: beta2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-12-23 01:41:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Upstream patch for the problem. (639 bytes, patch)
2006-10-25 16:00 UTC, Glauber Costa 		no flags Details | Diff
View All

Description Glauber Costa 2006-10-25 16:00:51 UTC 
When blkdev_name_to_number() fails to assign a number to the specified
device, it returns None, causing a far-away-from-self-explanatory
message to be delivered. 

To reproduce it, just try to use a nonexistant device, like xda instead of xvda.
You'll never guess what the real problem is.
Comment 1 Glauber Costa 2006-10-25 16:00:52 UTC 
Created attachment 139363 [details]
Upstream patch for the problem.
Comment 2 RHEL Program Management 2006-10-26 18:58:01 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 3 Rik van Riel 2006-11-09 02:48:01 UTC 
No QA ack yet :(
Comment 5 Jay Turner 2006-11-20 20:17:53 UTC 
QE ack for RHEL5.
Comment 6 Glauber Costa 2006-12-07 10:23:50 UTC 
This is already in the tree. Rik may have forgotten to set it modified. I'm
doing it.
Comment 7 RHEL Program Management 2006-12-23 01:41:17 UTC 
A package has been built which should help the problem described in 
this bug report. This report is therefore being closed with a resolution 
of CURRENTRELEASE. You may reopen this bug report if the solution does 
not work for you.
Note You need to log in before you can comment on or make changes to this bug.