Re: [Bug 194749] New: kernel bonding does not work in a network nameservice in versions above 3.10.0-229.20.1

2017-03-03 Thread Dan Geist
- On Mar 3, 2017, at 11:03 AM, Jiri Pirko j...@resnulli.us wrote: > Fri, Mar 03, 2017 at 04:19:13PM CET, nicolas.dich...@6wind.com wrote: >>Le 02/03/2017 à 21:39, Dan Geist a écrit : >>> - On Mar 2, 2017, at 3:11 PM, Cong Wang xiyou.wangc...@gmail.com wrote >>>

Re: [Bug 194749] New: kernel bonding does not work in a network nameservice in versions above 3.10.0-229.20.1

2017-03-02 Thread Dan Geist
TYPE=Ethernet BOOTPROTO=none DEVICE=p4p2 ONBOOT=yes MASTER=bond0 SLAVE=yes UUID=15135328-12b8-4fe3-8940-db02b77b94d9 NAME=p4p2 [root@01 network-scripts]# cat ifcfg-bond0 DEVICE=bond0 TYPE=Bond BONDING_MASTER=yes NAME=bond0 UUID=97674993-0e50-4a00-a210-c66d75481a84 ONBOOT=yes BONDING_OPTS="updelay=0 resend_igmp=1 use_carrier=1 miimon=100 downdelay=0 xmit_hash_policy=0 primary_reselect=0 fail_over_mac=0 arp_validate=0 mode=active-backup lacp_rate=0 arp_interval=0 ad_select=0" IPV6INIT=no Perhaps by not instantiating the bond interface until after the netns is created, this situation can be avoided? Thanks. Dan -- Dan Geist dan(@)polter.net