Bug 677900 - [TestOnly] storage device drivers regression testing for 5.7 alpha
Summary: [TestOnly] storage device drivers regression testing for 5.7 alpha
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Gris Ge
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-16 08:44 UTC by Qian Cai
Modified: 2011-06-02 08:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-02 08:37:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Qian Cai 2011-02-16 08:44:45 UTC 
Description of problem:
Storage device drivers BZs is the second largest group (after networking device drivers) in all approved kernel BZs in 5.7. This is a request to regression test those key storage device drivers. This could be a subset of Evan's priority hardware - storage testing.
Comment 1 RHEL Program Management 2011-02-18 03:40:19 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 3 Qian Cai 2011-03-31 06:41:09 UTC 
This needs sign-off from kdump testing as well.
Comment 4 Gris Ge 2011-05-10 13:32:12 UTC 
Take it.
Will work on at once.
Comment 6 Gris Ge 2011-05-20 07:46:42 UTC 
Both qla2xxx and lpfc pass the HBA test again RHEL 5.7 kernel -261.

Boot from SAN passed for lpfc and qla2xxx.

For NetApp LUN, submited a bug for adding new LUN: Bug #705682

For dev_loss_tmo, kernel error message flooding issue: Bug #706309
Comment 7 Gris Ge 2011-05-20 08:04:43 UTC 
verify
Note You need to log in before you can comment on or make changes to this bug.