Bug 505007 - dmraid regression on raid45 target kernel status interface
Summary: dmraid regression on raid45 target kernel status interface
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: dmraid
Version: 5.4
Hardware: All
OS: Linux
high
high
Target Milestone: beta
: ---
Assignee: Heinz Mauelshagen
QA Contact: Corey Marthaler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-10 11:06 UTC by Heinz Mauelshagen
Modified: 2009-09-02 11:16 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-02 11:16:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2009:1347 0 normal SHIPPED_LIVE dmraid bug-fix and enhancement update 2009-09-01 10:47:31 UTC

Description Heinz Mauelshagen 2009-06-10 11:06:43 UTC
Description of problem:
dmraid fails to retrieve state properly, because recent event registration fixes introduced into rc don't interpret paramater count reported via the raid45 target interface properly.

Version-Release number of selected component (if applicable):
dmraid-1.0.0.rc13-46.el5

How reproducible:
Always on RAID set activation.

Steps to Reproduce:
1. Activate intact RAID set
2. Check for error message on registration
3.
  
Actual results:
Error message

Expected results:
No error message with intact RAID set

Additional info:

Comment 8 Dean Jansa 2009-06-23 15:21:11 UTC
Due to lack of HW we would appreciate feedback from Partner

Comment 9 Chris Ward 2009-07-03 18:45:35 UTC
~~ Attention - RHEL 5.4 Beta Released! ~~

RHEL 5.4 Beta has been released! There should be a fix present in the Beta release that addresses this particular request. Please test and report back results here, at your earliest convenience. RHEL 5.4 General Availability release is just around the corner!

If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.

Please do not flip the bug status to VERIFIED. Only post your verification results, and if available, update Verified field with the appropriate value.

Questions can be posted to this bug or your customer or partner representative.

Comment 10 Chris Ward 2009-07-10 19:14:16 UTC
~~ Attention Partners - RHEL 5.4 Snapshot 1 Released! ~~

RHEL 5.4 Snapshot 1 has been released on partners.redhat.com. If you have already reported your test results, you can safely ignore this request. Otherwise, please notice that there should be a fix available now that addresses this particular request. Please test and report back your results here, at your earliest convenience. The RHEL 5.4 exception freeze is quickly approaching.

If you encounter any issues while testing Beta, please describe the issues you have encountered and set the bug into NEED_INFO. If you encounter new issues, please clone this bug to open a new issue and request it be reviewed for inclusion in RHEL 5.4 or a later update, if it is not of urgent severity.

Do not flip the bug status to VERIFIED. Instead, please set your Partner ID in the Verified field above if you have successfully verified the resolution of this issue. 

Further questions can be directed to your Red Hat Partner Manager or other appropriate customer representative.

Comment 12 errata-xmlrpc 2009-09-02 11:16:23 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1347.html


Note You need to log in before you can comment on or make changes to this bug.