Release Notes

Fixes

Topics:

• Dmesg displays Integrity Measurement Architecture (IMA) driver related-messages during system boot

•

After every reboot, the network interface name changes

• Red Hat Enterprise Linux Version 8 installation wizard creates a duplicate bonding interface

• Servers with the AMD Rome processor display a CCP initialization failure message in dmesg

• PowerEdge servers with the AMD Rome processor fail to detect an NVMe drive after multiple hot plugs

• Operating system enters the dracut shell during boot

• System crashes when rebooted with SR-IOV-enabled QLogic cards

• After system reboot, Disk data format (DDF) devices are not listed in /proc/mdstat

• Updating NVMe firmware using the nvme-cli utility displays an error in dmesg

• Fatal error BDF 02:00.0 is detected with BCM574xx NICs

• NVMe devices are not detected after hot-plugging

• Linux operating system fails to detect the Intel x710 card

• Dmidecode displays OUT OF SPEC in Slot Type and Slot Length of SMBIOS system slots

• Custom partitioning fails with FC LUN

• When booting the system from iSCSI with Mellanox CX-4 and CX-5 adapters, the system reports csum failure message

• Red Hat Enterprise Linux 8 kernel panic is observed due to fatal hardware error

Dmesg displays Integrity Measurement Architecture

(IMA) driver related-messages during system boot

Description:

Dmesg displays the following IMA driver related messages during system boot when the TPM 2.0 chip is

enabled with a SHA-256 algorithm:

ima: Allocated hash algorithm: sha1

ima: Error Communicating to TPM chip

Applies to: Red Hat Enterprise Linux 8.1 and later

Cause: The Integrity Measurement Architecture (IMA) driver currently supports the SHA-1 algorithm only.

Solution: Issue is resolved in Red Hat Enterprise Linux 8.3

Systems

affected:

Dell EMC PowerEdge yx4x and yx5x servers

Tracking number: 165260

After every reboot, the network interface name

changes

Description:

Network interfaces for NICs plugged into the PCI slot are named incorrectly. The issue could manifest

where interfaces are named as ethN instead of the expected ensXfY format, or the network interface is

incorrectly named. For example, the network interface is named ens5f0 when it is plugged into slot

number 4.

Applies to: Red Hat Enterprise Linux 8.1

Fixes 9