Bug 329011 - RHBA reference Galaxy, should reference IBM eHCA
Summary: RHBA reference Galaxy, should reference IBM eHCA
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: Documentation
Version: 5.0
Hardware: All
OS: Linux
urgent
high
Target Milestone: ---
: ---
Assignee: Brian Forte
QA Contact: Content Services Development
URL: http://rhn.redhat.com/errata/RHBA-200...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-12 05:36 UTC by Wade Mealing
Modified: 2014-06-18 07:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-24 23:51:09 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 37635 0 None None None Never

Description Wade Mealing 2007-10-12 05:36:01 UTC
Description of problem:

As of: http://rhn.redhat.com/errata/RHBA-2007-0736.html

 * HTS can detect Galaxy InfiniBand network devices.

We would like this changed to:

 * HTS can detect IBM eHCA InfiniBand network devices.

the name 'Galaxy' is an IBM Internal product name, and would not mean anything
to a customer.  As such, a customer is not likely to recognize it as relevant to
them.  A owner or user of an eHCA device would recognize the name eHCA.

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

Fri Oct 12 03:27:56 EST 2007

Comment 3 Brian Forte 2007-10-24 03:35:09 UTC
I've edited the incorrect text (and corrected a few typos for good measure) at 
<http://errata.devel.redhat.com/errata/show/6011> and approved the corrected text.

I can't, however, re-publish the note.

A ticket has been raised with Release Engineering re re-publishing the note:
<https://engineering.redhat.com/rt3/Ticket/Display.html?id=17207>


Comment 4 Brian Forte 2007-10-24 23:51:09 UTC
Errata has been re-published. Corrected text is now public-facing, replacing the previous erroneous 
copy.


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