Dell EMC PowerEdge Systems Running Red Hat Enterprise Linux 8 Release Notes June 2021 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2019-2021 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Release summary..........................................................................................................5 Version................................................................................................................................................................................... 5 Release date........................................................................................................................................................................
When booting the system from iSCSI with Mellanox CX-4 and CX-5 adapters, the system reports csum failure message................................................................................................................................................... 20 Red Hat Enterprise Linux 8 kernel panic is observed due to fatal hardware error........................................... 20 Chapter 6: Known issues....................................................................................................
1 Release summary Red Hat Enterprise Linux (RHEL) 8 is the follow-on Operating System (OS) release to the RHEL 7 operating system. Major enhancements in RHEL 8 are improvements in security and stability. Topics: • • • Version Release date Priority and recommendations Version 8.4 Release date May 2021 Priority and recommendations RECOMMENDED: Dell EMC recommends applying this update during your next scheduled update cycle.
2 Compatibility RHEL 8 is available on the 64-bit Intel architecture. Topics: • System configuration requirements System configuration requirements For detailed system configuration requirements for RHEL 8, see the documentation at www.redhat.com/support. Memory The following table lists the system memory requirements for the x86_64 architecture of RHEL 8. Table 1. Memory requirements for x86_64 architecture Memory Size Minimum recommended system memory 1.
3 New and enhanced in RHEL 8 release ● ● ● ● ● ● ● ● ● ● Simple content structure available through BaseOS and Application Stream repository More life cycle options and frequent application updates YUM4 package manager is based on the DNF technology Increased security with memory Better management of System Processes Support for Control Group v2 mechanism Multiple packages of the kernel package Distributed with Stratis, a new local storage manager, which provides easy to use CLI and well designed API Syste
4 Important notes In the earlier versions of Red Hat Enterprise Linux, the default network interface naming scheme was biosdevname. From RHEL 8 onwards, systemd is the default naming scheme for network interface naming. NOTE: You can turn on the biosdevname naming scheme during installation or post installation by passing the kernel command line parameter biosdevname=1.
5 Fixes Topics: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • BIOS update does not complete when an update is performed using the Linux .BIN files Dmesg shows drm related call trace in RHEL 8.3 Operating system crashes on servers with NVIDIA GPGPUs Dmesg and /var/log/messages display AMD-Vi related messages The status of the NetworkManager service may be inactive when RHEL 8.
Dmesg shows drm related call trace in RHEL 8.3 Description: On a Dell EMC PowerEdge MX740C system installed with RHEL 8.3, following call trace is observed in Dmesg. For more information, see Red Hat Enterprise Linux Knowledge Base article 5899381. WARNING: CPU: 102 PID: 1722 at drivers/gpu/drm/drm_gem_vram_helper.c:576 Applies to: Red Hat Enterprise Linux 8.3 Workaround: Not available. The message can be ignored. Solution: The issue is resolved in Red Hat Enterprise Linux 8.
The status of the NetworkManager service may be inactive when RHEL 8.3 is rebooted Description: The status of the NetworkManager service may be inactive when the operating system is rebooted. The issue is observed when the Performance Co-Pilot (PCP) package is installed on the operating system. The command systemctl status NetworkManager can be used to check the status of the service. For more information, see Red Hat Enterprise Linux Knowledge Base article 5394191.
The mdmonitor service displays an error during operating system installation Description: When the operating system is installed on a virtual disk that is created by Dell EMC S150 RAID Controller, the following error message is observed during installation: [FAILED] Failed to start Software RAID monitoring and management This issue is a cosmetic issue and can be ignored. The operating system installation completes successfully.
Disk drives part of MD RAID are not listed as installation destination by the installer Description: During installation, if a disk drive which was previously part of MD RAID volume is used, it is not listed as an installation destination by the operating system installer. Applies to: Red Hat Enterprise Linux 7.0 and later. Solution: The drive must be formatted. For more information, see Red Hat Enterprise Linux Knowledge Base article 5801081.
Guest VMs with SRIOV VFs assigned take a long time to power on, and libvirt related errors are observed Description: On a system with multiple guest VMs running storage I/O and network IO operations, VMs with SRIOV VFs assigned take a long time to power on. When the issue occurs, following error message is logged in /var/log/messages continuously until the guest VM successfully powers on.
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 Cause: There is an issue with _SUN ACPI Slot numbers in system firmware. Solution: Update the system BIOS to 1.4.8 version or later.
Workaround: NOTE: The output of each command varies based on your system configuration. Follow the steps: 1. Identify the parent device to which the NVMe device is connected using the following command: lspci -t -+-[0000:e0]-+-00.0 | +-00.2 | +-01.0 | +-02.0 | +-03.0 | +-03.1-[e2]----00.0 From the above snippet, the device e2:00.0 is the NVMe device and the device e0:03.1 is the parent device. The parent device is used for the steps that are described subsequently. 2.
System crashes when rebooted with SR-IOV-enabled QLogic cards Description When the system is rebooted with SR-IOV-enabled QLogic cards, the system crashes and generates a coredump (vmcore) in /var/crash. Applies to Red Hat Enterprise Linux 7.6 and later Cause: The system crash is due to an issue in the qede driver. Workaround Disable SR-IOV before rebooting the system.
Tracking number: 158536 Fatal error BDF 02:00.0 is detected with BCM574xx NICs Description: A fatal error on bus number 02, device number 00, and function number 0 (BDF 2:0.0) is observed in the following configurations: ● When a graceful shutdown action is initiated. ● In Gnome settings, under the Suspend & Power Button section, the When the Power Button is pressed option is set to Suspend. Applies to: Red Hat Enterprise Linux 8.
Vendor ID: 8086 Device ID: 15FF Applies to: Red Hat Enterprise Linux 7.7 and later Cause: The i40e in-box driver is not enabled to detect an Intel x710 NIC. Workaround: Install the out-of-box drivers. Solution: The issue is resolved in Red Hat Enterprise Linux 8.
When booting the system from iSCSI with Mellanox CX-4 and CX-5 adapters, the system reports csum failure message Description: When booting the system from iSCSI with Mellanox CX-4 and CX-5 adapters, the following message is displayed in the dmesg and /var/log/messages reports: localhost kernel: ibft0: hw csum failure This message can be ignored. Applies to: Cause: Some networking switches which are sending frames with nonzero padding bytes maybe causing the issue.
6 Known issues Topics: • • • • • • • • • • • • • • • • • • • • • • • • • • • System hangs when Intel tboot is used to boot the operating system The anaconda installer crashes while autoconfiguring disk partitions The version field in the output of the modinfo command for certain networking drivers is null NetworkManager may restart unexpectedly when creating greater than 256 VLAN devices configured with DHCP IP FCoE session is not reestablished after MX9116N switch is rebooted Dmesg displays error messages
The anaconda installer crashes while autoconfiguring disk partitions Description: On a drive with older GPT metadata, the anaconda installer crashes while autoconfiguring disk partitions. The following messages are observed in syslog every time a disk is discovered: WARNING kernel:GPT:Primary header thinks Alt. header is not at the end of the disk. WARNING kernel:GPT:209715199 != 282407679 WARNING kernel:GPT:Alternate GPT header not at the end of the disk.
NetworkManager may restart unexpectedly when creating greater than 256 VLAN devices configured with DHCP IP Description: On RHEL 8.3, when more than 256 VLAN devices are created and configured with DHCP IP, NetworkManager utility may restart unexpectedly resulting in not creating expected number of VLAN devices and some VLAN interfaces may not receive DHCP IP. Applies to: Red Hat Enterprise Linux 8.0 and later Workaround: 1.
Dmesg displays error messages when NVMe device is surprise removed Description: Dmesg or /var/log/messages show the following error messages after an NVMe device is unbound from the NVMe driver and surprise removed: kernel: pcieport 0000:b0:06.0: Timeout waiting for Presence Detect kernel: pcieport 0000:b0:06.0: link training error: status 0x8001 kernel: pcieport 0000:b0:06.0: Failed to check link status Applies to: Red Hat Enterprise Linux 8.
Tracking number: 182820 Dell Controlled Turbo feature is not functional Description: Dell Controlled Turbo is not functional when the system profile setting in BIOS is set to performance or custom. Applies to: Red Hat Enterprise Linux 8.0 and later Cause: The intel_pstate driver may interfere with the processor settings which results in Dell Controlled Turbo feature being not functional. Solution: Prevent the intel_pstate driver from loading.
The output of the systemctl status command displays the status as thawing Description: The output of the systemctl status command displays the status Active: active (running) (thawing) instead of Active: active (running) when a service is reloaded. This issue is a cosmetic issue and can be ignored. Applies to: Red Hat Enterprise Linux 8.
The Mellanox IB devices are listed under an incorrect device category on Red Hat Enterprise Linux 8 Description: The Mellanox IB devices are listed under the Bluetooth section of the Network settings tab in Red Hat Enterprise Linux 8 and Red Hat Enterprise Linux 8.1 operating systems. This is a cosmetic issue and can be ignored. Applies to: Red Hat Enterprise Linux 8 and later Workaround: Use the nmcli tool or the nm-connection-editor to display available devices.
Dmesg displays TPM and nvdimm related-messages in Red Hat Enterprise Linux 8.1 Description: When Red Hat Enterprise Linux Version 8.1 is booted with the TPM 2.0 chip enabled, dmesg displays the following messages in var/log/message: No TPM handle discovered. failed to open file /etc/ndctl/keys/nvdimm-master.blob: No such file or directory There is no impact to the functionality of the TPM chip if it is enabled in the system BIOS. This is a cosmetic error and can be ignored.
iscsiadm output displays STATIC in the iface.bootproto field when the network interface is configured to DHCP Description: When the system is booting from iSCSI with the Emulex OneConnect device that is configured with DHCP IP, the iface.bootproto field is listed as STATIC in the command iscsiadm -m fw output. There is no functionality loss. Applies to: Red Hat Enterprise Linux 7.
2. In the Suspend & Power Button section, from the When the Power Button is pressed list, select Power Off. NOTE: By default, Suspend option is selected. NOTE: The preceding workaround may not work when the system is locked. GNOME prevents the accidental shutdown when system is locked.
Systems affected: All Dell EMC PowerEdge servers Tracking number: 124792 RHEL 8 installation fails on systems with Emulex OneConnect card Description: When RHEL 8 is installed on an iSCSI LUN that is configured on Emulex OneConnect card on Dell EMC 13G systems, the installation fails with a UnicodeDecodeError. This error occurs because the Anaconda installer is unable to decode the iSCSI initiator name. Applies to: RHEL 8.
7 Limitations ● ● ● ● ● The auth and authconfig kickstart commands require the AppStream repository The --interactive option of the ignoredisk kickstart command does not work in RHEL 8 RHEL 8 system becomes unresponsive when many devices are connected Physical memory hot plugging does not work Database servers are not installable in parallel For more information on the limitations of RHEL 8, see www.access.redhat.com/documentation/en-us/ red_hat_enterprise_linux/8/html-single/8.
8 Resources and support This section provides information about the documentation resources for your server. Table 2. Additional documentation resources for your server Task Document Location Setting up your server For information about installing the server into a rack, see the Rack documentation included with your rack solution or the Getting Started Guide that is shipped with your server. https://www.dell.
Table 2. Additional documentation resources for your server (continued) Task Document Location the Dell EMC www.dell.com/ openmanagemanuals > OpenManage Essentials User’s Guide. For information about installing and using Dell SupportAssist, see the Dell EMC SupportAssist Enterprise User's Guide. https://www.dell.com/serviceabilitytools For understanding the features of Dell EMC Lifecycle Controller (LC), see the Lifecycle Controller User's Guide. https://www.dell.
Download drivers and firmware It is recommended that you download and install the latest BIOS, drivers, and systems management firmware on your system. Ensure that you clear the web browser cache before downloading the drivers and firmware. 1. Go to Dell.com/support/drivers. 2. In the Drivers & Downloads section, enter the Service Tag of your system in the Enter a Dell Service Tag, Dell EMC Product ID, or Model field, and then click Submit.
9 Contacting Dell EMC Dell EMC provides several online and telephone-based support and service options. Availability varies by country, region, and product, and some services may not be available in your area. To contact Dell EMC for sales, technical assistance, or customer service issues, see https://www.dell.com/contactdell. If you do not have an active Internet connection, you can find contact information on your purchase invoice, packing slip, bill, or the product catalog.
