Release Notes

While adding second slave to bond, it asks for
connection type and shows additional connection
types
Description: To create the bonding interference between the master and the slave, slave asks for connection type and
displays additional connection types.
Applies to: Red Hat Enterprise Linux 7.0
Cause: Network manager does not filter the type of connection required for the slave.
Workaround: This issue can be ignored because there is no functionality loss.
Loopback device is displayed as unknown in network
settings
Description: Network setting of local host displayed as unknown for loopback interface.
Applies to: Red Hat Enterprise Linux 7.0
Cause: Network manager does not manage the loopback interface.
Workaround: This issue can be ignored because there is no functionality loss.
Kernel panic on reboot or shutdown when Mellanox
Team is setup
Description:
Rebooting the system results in kernel panic, when the system has a bonding device with Mellanox
ConnectX-3 devices as slaves.
Applies to: Red Hat Enterprise Linux 7.0
Cause: Kernel panic occurs when Mlx4_ib driver accesses the slave data structure that is already freed during
the restart.
Workaround: Ensure that Mlx4_ib driver is unloaded before reboot.
PCIeSSDs report incorrect pciehp messages during
boot
Description:
During Red Hat Enterprise Linux 7 bootup, pciehp related messages are displayed even when there are no
hotplug activity: pciehp 0000:82:05.0:pcie24: Device 0000:84:00.0 already exists
at.
Applies to: Red Hat Enterprise Linux 7.0
Cause: While booting kernel attempts to add a preexisting device prior moving to the suspend state.
Workaround: This error message can be ignored because there is no functionality loss.
Known issues 41