Dell EMC PowerEdge Systems Running Red Hat Enterprise Linux 8 Release Notes May 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........................................................................................................................................................................
The lvcreate command requests a response from the user when -wipesignature -yes parameters are passed.............................................................................................................................................................................. 20 The mdmonitor service displays an error during operating system installation................................................. 20 The dmidecode utility displays the slot type as for PCIe Gen 4 NVMe slots.................
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.3 Release date November 2020 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: • • • • • • • • • • • • • • • • • • • • The mcelog utility logs 'only decoding architectural errors' message in var/log/messages Disk drives part of MD RAID are not listed as installation destination by the installer Dell EMC OpenManage Storage Services utility fails to reconfigure the virtual disk Guest VMs with SRIOV VFs assigned take a long time to power on, and libvirt related errors are observed Dmesg displays Integrity Measurement Architecture (IMA) driver related-messages during syst
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: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Operating system crashes on systems 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.
Systems affected: All Dell EMC PowerEdge systems which support Nvidia GPGPUs Tracking number: 189163 Dmesg and /var/log/messages display AMD-Vi related messages Description: Dmesg and /var/log/messages display the following messages on Dell EMC PowerEdge servers with 256 core CPUs and Dell EMC PowerEdge Express Flash Enterprise NVMe Agnostic (AGN) device or Dell EMC Express Flash Enterprise NVMe CD6 or Dell EMC Express Flash Enterprise NVMe CM6 device: AMD-Vi: Failed to allocate IRTE The message indicat
Tracking number: 179019 The lvcreate command requests a response from the user when -wipesignature -yes parameters are passed Description: The lvcreate command requests a response from the user when -wipesignature -yes parameters are passed. When -yes parameter is passed, lvcreate is not expected to prompt the user for a response. Applies to: Red Hat Enterprise Linux 8.0 and later Workaround: Use the wipefs command to clear the signatures before reusing the space for Logical Volume Manager (LVM).
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 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. 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. Systems affected: Dell EMC PowerEdge MX740C.
/proc/mdstat and mdadm -D commands display incorrect statuses when two NVMe devices are surprise removed from a RAID 5 MD array Description: When two of three NVMe devices are surprise removed from a RAID 5 MD array, the command cat/ proc/mdstat displays the array status incorrectly as active. Similarly, when the status of the MD RAID is queried using the mdadm -D /dev/mdN command, the number of active and working devices that are displayed is two. Only the status of the array reported is incorrect.
RHEL 8.3 installer does not automatically locate the source installation repository when only inst.stage2=hd boot option is used Description: When both stage2 and the installation repository are on the same internal drive or external drive (USB hard drive), RHEL 8.3 installer does not automatically locate the source installation repository when only inst.stage2=hd boot option is used. Applies to: Red Hat Enterprise Linux 8.3 Workaround: Modify the boot option inst.stage2=hd:LABEL= to inst.
Drivers available in OEMDRV drive are not installed during the operating system installation Description: Intermittently, during the installation of Red Hat Enterprise Linux, the operating system cannot enumerate the USB drive at the stage of driver disk probing. This prevents the drivers from LC/OEMDRV from being installed. Applies to: Red Hat Enterprise Linux 8 and later Workaround: Use the kernel boot parameter command inst.dd=LABEL=OEMDRV to install the drivers in the OEMDRV drive.
Driver dependency mismatch errors reported while installing out-of-box drivers on Red Hat Enterprise Linux 8.x Description: Driver dependency mismatch errors are reported when inst.dd installation methods (flash drive, driver package, HTTP, NFS, FTP) are used to install the out-of-box (OOB) drivers during operating system installation. The dependency errors are not observed after the initial installation as the operating system will use the out-of-box (OOB) drivers.
Tracking number: 160773 Mellanox InfiniBand adapters are listed in Bluetooth Description: Mellanox InfiniBand adapters are listed in Gnome, under the Network > Settings > Bluetooth section. Applies to: Red Hat Enterprise Linux 8.0 and later Cause: Not available Workaround: Not available. This issue is a cosmetic issue. Use other tools like nmcli, and nm-connection-editor to view and configure the InfiniBand interfaces.
Unable to shut down RHEL 8 when you select Graceful shutdown option or when you press power button on the server Description: When you select the Graceful shutdown option from any system management interface such as iDRAC or press the power button, the system goes to suspended state and stops all the tasks. So, firmware updates through iDRAC interface that require restart take longer, and the system is hard reset upon iDRAC watchdog time expiration. Applies to: Red Hat Enterprise Linux 8.
iSCSI LUN not discovered during RHEL 8 installation Description: When Red Hat Enterprise Linux 8 is installed on an iSCSI LUN, the LUN is not discovered automatically. Applies to: Red Hat Enterprise Linux 8.0 Cause: If the Network interface displays the status as UP but displays NO-CARRIER, it indicates that dracut has reduced the wait time to run the network interface from 7 seconds to 5 seconds.
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.
