Begin forwarded message:
Date: Wed, 01 Mar 2017 21:08:01 +0000 From: bugzilla-dae...@bugzilla.kernel.org To: step...@networkplumber.org Subject: [Bug 194749] New: kernel bonding does not work in a network nameservice in versions above 3.10.0-229.20.1 https://bugzilla.kernel.org/show_bug.cgi?id=194749 Bug ID: 194749 Summary: kernel bonding does not work in a network nameservice in versions above 3.10.0-229.20.1 Product: Networking Version: 2.5 Kernel Version: > 3.10.0-229.20.1 Hardware: x86-64 OS: Linux Tree: Mainline Status: NEW Severity: blocking Priority: P1 Component: Other Assignee: step...@networkplumber.org Reporter: d...@polter.net Regression: No bond interface is being used in active/standby mode with two physical NICs inside a network nameservice to provide switchpath redundancy. netns is instantiated post-boot with the following: ip netns add vntp ip link set p4p1 netns vntp ip link set p4p2 netns vntp ip link set bond0 netns vntp ip netns exec vntp ip link set lo up ip netns exec vntp ip link set p4p1 up ip netns exec vntp ip link set p4p2 up ip netns exec vntp ip link set bond0 up ip netns exec vntp ifenslave bond0 p4p1 p4p2 This works as one would expect in kernel versions up to 3.10.0-229.20.1 (CentOS 7 packages). At the next patchlevel and all subsequent versions released by the packager, the following appears in system logs and the bond0 instantiation fails: Mar 1 19:33:42 fed1ntpi01 rc.local: Cannot find device "bond0" Mar 1 19:33:42 fed1ntpi01 rc.local: Master 'bond0': Error: handshake with driver failed. Aborting Mar 1 19:33:42 fed1ntpi01 rc.local: Cannot find device "bond0" Mar 1 19:33:42 fed1ntpi01 rc.local: Cannot find device "bond0" -- You are receiving this mail because: You are the assignee for the bug.
