Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1043372

Summary: Could not copy firmware file /tmp/DD/lib/firmware/updates: Is a directory
Product: Red Hat Enterprise Linux 6 Reporter: Weiping Pan <wpan>
Component: anacondaAssignee: Brian Lane <bcl>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.4CC: ccui, lwang, mganisin, pholica, qzhao, ruyang, sbueno, wpan
Target Milestone: rc   
Target Release: 6.6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: anaconda-13.21.216-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-14 06:39:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1023566    
Attachments:
Description Flags
DUP for bnx2x
none
anaconda.log
none
boot failure picture
none
patch none

Description Weiping Pan 2013-12-16 06:29:40 UTC 
Description of problem:

dd-bnx-16235-x86_64.iso has five drivers, which are cnic, bnx2, bnx2x, bnx2i and bnx2fc, and two firmware packages, which are kmod-bnx2-firmware and kmod-bnx2x-firmware.

I am trying to install a RHEL6.4 system with DUP on iscsi target via bnx2x card,
but during installation, Anaconda logged a ERROR in anaconda.log,
"ERROR   : Could not copy firmware file /tmp/DD/lib/firmware/updates: Is a directory"

And I find that only the files in kmod-bnx2-firmware package are in the new initramfs, while the files in kmod-bnx2x-firmware are not in the new initramfs. 
So when reboot, it will say 
"bnx2x 0000:08:00.0: firmware: requesting bnx2x/bnx2x-e1h-7.8.17.0.fw
bnx2s: [bnx2x_init_firmware:12436(eth0)] Can't load firmware file bnx2x/bnx2x-e1h-7.8.17.0.fw", then the boot failed.

It seems that at present Anaconda can only hanle one firmware package.

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

How reproducible:


Steps to Reproduce:
1.install a RHEL6.4 system with DUP on iscsi target via bnx2x card
2.reboot
3.boot failure

Actual results:
boot failure

Expected results:
boot success

Additional info:

hp-dl380eg8-02.rhts.eng.nay.redhat.com
Comment 1 Weiping Pan 2013-12-16 06:30:56 UTC 
Created attachment 837117 [details]
DUP for bnx2x
Comment 2 Weiping Pan 2013-12-16 06:31:32 UTC 
Created attachment 837118 [details]
anaconda.log
Comment 3 Weiping Pan 2013-12-16 06:32:54 UTC 
Created attachment 837119 [details]
boot failure picture
Comment 4 Brian Lane 2013-12-17 22:58:55 UTC 
Give this updates.img a try:

http://bcl.fedorapeople.org/updates/1043372.img

We weren't copying the firmware/updates/* files over to the target system before recreating the initrd so they were missing.

Also note, the dd iso you attached is the wrong one, it is for rhel7.
Comment 5 Brian Lane 2013-12-18 19:04:48 UTC 
Created attachment 838536 [details]
patch
Comment 6 Weiping Pan 2013-12-20 02:55:28 UTC 
(In reply to Brian C. Lane from comment #4)
> Give this updates.img a try:
> 
> http://bcl.fedorapeople.org/updates/1043372.img
> 
> We weren't copying the firmware/updates/* files over to the target system
> before recreating the initrd so they were missing.

Agreed.

> 
> Also note, the dd iso you attached is the wrong one, it is for rhel7.

No, it is for RHEL6.4, it is built against 2.6.32-358.
Comment 7 Weiping Pan 2013-12-20 03:00:06 UTC 
(In reply to Brian C. Lane from comment #5)
> Created attachment 838536 [details]
> patch

I think your patch is fine, and I will test it when it is merged.

thanks
Weiping Pan
Comment 8 RHEL Program Management 2014-03-26 00:14:41 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release.  Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Comment 14 errata-xmlrpc 2014-10-14 06:39:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-1380.html