Page MenuHomeVyOS Platform
Create Task
Maniphest T2030

Bond doesn't survive reboot
Closed, ResolvedPublicBUG
Actions

Description

I have a test setup:

interfaces {

bonding bond0 {
    description "Core: XXX"
    member {
        interface eth6
        interface eth7
    }
    mode 802.3ad
    mtu 9000
    vif 3331 {
        address x.y.z.a/29
    }
}

}

and

ethernet eth6 {
    hw-id ac:1f:6b:6d:16:74
    mtu 9000
    offload-options {
        generic-receive on
        generic-segmentation on
        scatter-gather on
        tcp-segmentation on
        udp-fragmentation on
    }
}
ethernet eth7 {
    hw-id ac:1f:6b:6d:16:75
    mtu 9000
    offload-options {
        generic-receive on
        generic-segmentation on
        scatter-gather on
        tcp-segmentation on
        udp-fragmentation on
    }
}

this setup doesn't survive reboot ... it boots into bond state down:

$ cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: load balancing (round-robin)
MII Status: down
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0

But:

[email protected]:~$ configure
[email protected]# delete interfaces bonding bond0 member interface eth7
[email protected]# delete interfaces bonding bond0 member interface eth6
[email protected]# commit
[email protected]# set interfaces bonding bond0 member interface eth6
[email protected]# set interfaces bonding bond0 member interface eth7
[email protected]# commit

Solves the problem.

It doesn't work in 1.3-rolling-202002101915 and 1.3-rolling-202002120218. Similar setup does work in 1.3-rolling-202001261918.

There are no visible errors in log files.

Details

Difficulty level
Normal (likely a few hours)
Version
1.3-rolling-202002120218
Why the issue appeared?
Design mistake
Is it a breaking change?
Perfectly compatible
Issue type
Bug (incorrect behavior)

Related Objects

Event Timeline

primoz created this task.Feb 12 2020, 10:03 PM
Dmitry changed the task status from Open to Confirmed.Feb 12 2020, 10:38 PM
c-po changed the task status from Confirmed to In progress.Feb 15 2020, 1:11 PM
c-po claimed this task.
c-po added a comment.Feb 15 2020, 7:44 PM

There is a faulty delta check in interfaces-bonding.py leading to the fact that physical interfaces are not enslaved. As soon as they are enslaved all works (eth2 and eth3 in my case):

ip link set dev eth2 down
echo '+eth2' > /sys/class/net/bond0/bonding/slaves
ip link set dev eth3 down
echo '+eth3' > /sys/class/net/bond0/bonding/slaves
c-po closed this task as Resolved.Feb 16 2020, 9:58 AM
c-po triaged this task as High priority.
c-po changed Difficulty level from Unknown (require assessment) to Normal (likely a few hours).
c-po changed Why the issue appeared? from Will be filled on close to Design mistake.
c-po changed Is it a breaking change? from Unspecified (possibly destroys the router) to Perfectly compatible.
c-po added a comment.Feb 16 2020, 10:39 AM

Thanks for reporting this nasty issue. The fix is applied to rolling release starting with build: vyos-1.3-rolling-202002161021-amd64.iso

This issue is not present in 1.2 crux branch as it was introduced in the new Python interface code.

c-po mentioned this in T2043: Bond VLANs can't be extended on the fly.Feb 16 2020, 10:50 AM
pasik added a subscriber: pasik.Feb 16 2020, 8:31 PM
c-po moved this task from Need Triage to Finished on the VyOS 1.3 Equuleus board.Feb 17 2020, 6:57 PM
jjakob mentioned this in T2409: At boot, effective config should not be equal to current config.May 7 2020, 10:32 AM
erkin set Issue type to Bug (incorrect behavior).Aug 31 2021, 5:43 PM
syncer edited projects, added VyOS 1.3 Equuleus (1.3.0); removed VyOS 1.3 Equuleus.Aug 30 2022, 2:04 PM
syncer moved this task from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0) board.