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 1683387

Summary: [Diamanti]Programming the VF MAC address fails without updated FW [rhel-7.6.z]
Product: Red Hat Enterprise Linux 7 Reporter: RAD team bot copy to z-stream <autobot-eus-copy>
Component: linux-firmwareAssignee: Bruno Meneguele <brdeoliv>
Status: CLOSED ERRATA QA Contact: Network QE <network-qe>
Severity: high Docs Contact:
Priority: high    
Version: 7.7CC: brdeoliv, dhoward, feliu, gcase, jiji, kzhang, network-qe, rasibley, rvr, tumeya, venkatesh
Target Milestone: rcKeywords: OtherQA, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: linux-firmware-20180911-69.1.git85c5d90.el7_6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1671610 Environment:
Last Closed: 2019-10-29 14:02:14 UTC Type: ---
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: 1671610    
Bug Blocks:    

Description RAD team bot copy to z-stream 2019-02-26 18:37:15 UTC 
This bug has been copied from bug #1671610 and has been proposed to be backported to 7.6 z-stream (EUS).
Comment 6 Rachel Sibley 2019-07-23 12:43:44 UTC 
Hi Kexin, this missed the last z-stream batch, can someone from Network-QE help get this into the verified state ? Thanks!
Comment 7 Fei Liu 2019-07-24 08:13:24 UTC 
Vrified on linux-firmware-20180911-69.1.git85c5d90.el7_6.noarch.rpm. SanityOnly

Checking RPM content 
-rw-r--r--.  1 root root 179202 Feb 26 17:16 aq1202_fw.cld
-rw-r--r--.  1 root root 208900 Feb 26 17:16 bcm8483.bin
-rw-r--r--.  1 root root 539648 Feb 26 17:16 t4fw-1.14.4.0.bin
-rw-r--r--.  1 root root 541184 Feb 26 17:16 t4fw-1.15.37.0.bin
-rw-r--r--.  1 root root 565248 Feb 26 17:16 t4fw-1.22.9.0.bin
lrwxrwxrwx.  1 root root     17 Jul 24 04:01 t4fw.bin -> t4fw-1.22.9.0.bin
-rw-r--r--.  1 root root 593920 Feb 26 17:16 t5fw-1.14.4.0.bin
-rw-r--r--.  1 root root 596992 Feb 26 17:16 t5fw-1.15.37.0.bin
-rw-r--r--.  1 root root 652800 Feb 26 17:16 t5fw-1.22.9.0.bin
lrwxrwxrwx.  1 root root     17 Jul 24 04:01 t5fw.bin -> t5fw-1.22.9.0.bin
-rw-r--r--.  1 root root 703488 Feb 26 17:16 t6fw-1.22.9.0.bin
lrwxrwxrwx.  1 root root     17 Jul 24 04:01 t6fw.bin -> t6fw-1.22.9.0.bin
Comment 9 errata-xmlrpc 2019-10-29 14:02:14 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.

https://access.redhat.com/errata/RHBA-2019:3221