Bug 429325 - Need cmirror-kmod added to Cluster-Storage channel in RHEL5
Summary: Need cmirror-kmod added to Cluster-Storage channel in RHEL5
Keywords:
Status: CLOSED DUPLICATE of bug 456538
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: releng
Version: 5.2
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Dennis Gregorovic
QA Contact: Daniel Riek
URL:
Whiteboard:
Depends On: 373691
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-18 18:14 UTC by Chris Feist
Modified: 2008-09-05 16:45 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-05 16:45:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Chris Feist 2008-01-18 18:14:57 UTC
Need to get cmirror-kmod added to Cluster-Storage section of RHEL5 (not base
RHEL-5).

This is already being tested by Minneapolis QA.

Comment 1 Chris Feist 2008-01-18 19:34:15 UTC
Setting ack flags.  Also note, that this is not for base RHEL5, it's for the
Cluster Storage channels for RHEL5.

Comment 2 RHEL Program Management 2008-01-18 19:36:15 UTC
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".

Comment 6 RHEL Program Management 2008-06-02 20:24:33 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 9 Dennis Gregorovic 2008-09-05 16:45:47 UTC

*** This bug has been marked as a duplicate of bug 456538 ***


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