Bug 915284 - Mismatch of lpfc driver version between release notes & ISO
Summary: Mismatch of lpfc driver version between release notes & ISO
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: Documentation
Version: 6.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Martin Prpič
QA Contact: ecs-bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2013-02-25 11:35 UTC by Martin Young
Modified: 2013-02-26 12:56 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-02-26 12:56:22 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Martin Young 2013-02-25 11:35:31 UTC
Description of problem:

In the release notes for RHEL 6.4 at https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.4_Technical_Notes/ch-device_drivers.html the lpfc driver version is shown as follows: 
"The lpfc driver for Emulex Fibre Channel Host Bus Adapters has been updated to version".

However if I install RH6u4 the lpfc driver version is different:

[root@hpc7000-07-b7 Red_Hat_Enterprise_Linux-Release_Notes-6-en-US-4]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.4 (Santiago)
[root@hpc7000-07-b7 Red_Hat_Enterprise_Linux-Release_Notes-6-en-US-4]# modinfo lpfc | grep -i des
description:    Emulex LightPulse Fibre Channel SCSI driver

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


How reproducible:

Reproducable on install of RHEL6u4.GA.

Steps to Reproduce:
1. Install RHEL6u4.GA. 
2. modinfo lpfc | grep -i des
3. Refer to https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.4_Technical_Notes/ch-device_drivers.html 
Actual results:

Driver version between steps 2 and 3 will differ.

Expected results:

Driver version between steps 2 and 3 should correspond.

Additional info:

Comment 1 Martin Prpič 2013-02-25 11:41:38 UTC
Fixed! I'm building the new version now and it should be live in about 2 hours.

Thanks for reporting this error!


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