From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 194749] New: kernel bonding does not work in a network nameservice in versions above 3.10.0-229.20.1
Date: Thu, 2 Mar 2017 10:32:19 -0800 [thread overview]
Message-ID: <20170302103219.74b675c5@xeon-e3> (raw)
Begin forwarded message:
Date: Wed, 01 Mar 2017 21:08:01 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@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: stephen@networkplumber.org
Reporter: dan@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.
next reply other threads:[~2017-03-02 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 18:32 Stephen Hemminger [this message]
2017-03-02 20:11 ` Fw: [Bug 194749] New: kernel bonding does not work in a network nameservice in versions above 3.10.0-229.20.1 Cong Wang
2017-03-02 20:39 ` Dan Geist
2017-03-03 15:19 ` Nicolas Dichtel
2017-03-03 16:03 ` Jiri Pirko
2017-03-03 16:22 ` Dan Geist
2017-03-03 16:25 ` Nicolas Dichtel
2017-03-03 18:11 ` Cong Wang
2017-03-04 9:43 ` Jiri Pirko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170302103219.74b675c5@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox