Release Notes

Chipset watchdog device is not created when the OS
Watchdog Timer option is enabled in BIOS
Description: On the Dell EMC PowerEdge T140, R240, and T340 servers, if the OS Watchdog timer is enabled in BIOS,
then the watchdog device node is not created and watchdog does not run.
Applies to: Red Hat Enterprise Linux 7.5
Cause: Intel has replaced iTCO with the WDAT watchdog for these platforms. However, WDAT is not supported
on RHEL 7.5.
Workaround: Use BMC watchdog with the systems. For more information about how to setup system, see
www.dell.com/support/article/sln312339.
Systems with QLogic Cards that are configured with
VLAN over Bond fail to shutdown or reboot
Description: When a system is rebooted after creating the VLAN over a Bond on two ports of QLogic cards, the
reboot process stops and the following error message is displayed:
unregister_netdevice: waiting for <Network-Interface> to become free. Usage
count = 2.
Applies to: Red Hat Enterprise Linux 7.5
Cause: If RDMA devices are not removed before unregistering the NetDevice, the process of unregistering the
NetDevice is paused until the usage count becomes free. So, the system stops responding to reboot.
Solution: Upgrade the kernel to kernel-3.10.0-862.10.1.el7 or later.
Workaround: Before rebooting the system, bring down the Bond interface. For more information, see
www.access.redhat.com/solutions/3438871.
NetworkManager fails to bring up VLAN interface
created over Bond interface
Description:
When a VLAN interface is created over a Bond interface using nm-connection-editor, the
NetworkManger fails to bring up the interface at every boot.
Applies to: Red Hat Enterprise Linux 7.5
Cause: NetworkManager fails to automatically activate child connections when it does not manage the parent
device. While booting the system, the NetworkManager looks for the parent device of VLAN connections,
and skips the unmanaged Bond. So, the activation of VLAN interface fails.
Solution: Upgrade NetworkManager to NetworkManager-1.10.2-14.el7 or later.
Workaround: After booting the system, save the VLAN-over-Bond interface configuration again through nm-
connection-editor to bring up the interface. You can also use the nmcli utility to create VLAN over
Bond configuration.
Known issues 21