Bonding "parameters" not supported

Bug #1781203 reported by carlos
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Netplan
Confirmed
Undecided
Unassigned

Bug Description

I have the next configuration:

# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    version: 2
    renderer: networkd

    ethernets:
        eno1:
            addresses:
            - 192.168.3.x/24
            gateway4: 192.168.x.1
            nameservers:
                addresses:
                - 192.168.2.2
                search:
                - xxx.xxx
        enp7s0f0:
          dhcp4: no
        enp7s0f1:
          dhcp4: no

    bonds:
      bond0:
        dhcp4: no

        interfaces:
          - enp7s0f0
          - enp7s0f1
        addresses:
          - 192.168.x.10/24
        parameters:
          mode: 802.3ad
          mii-monitor-interval: 1

When i tried try with netplan try:
root@xxx:~# netplan try
bond0: reverting custom parameters for bridges and bonds is not supported

Please carefully review the configuration and use 'netplan apply' directly.

So, the bonding configuration default is "round-robin", and i need 802.3ad. But netplan say that "parameters" are not allowned...

carlos (nitrosito)
description: updated
Revision history for this message
Damon Dransfeld (skibaprocomputer) wrote :

I encountered the same issue. My config is attached.
The "reverting custom parameters for bridges and bonds is not supported" error appeared with the same config that the machine was set up with (parameters were not altered).

Revision history for this message
carlos (nitrosito) wrote :

My fix:

- Remove netplan
- Install ifupdown
- Install resolvconf

Use traditional interfaces files

Revision history for this message
Ryan Harper (raharper) wrote :

The parameters are supported; but you cannot "try" that configuration out temporarily. The 'try' subcommand attempts to keep the current configuration around, generate and apply the "new" config, and allow you to confirm if things are working and if not, it will restore the original config prior to the try. One cannot "try" bond or bridge parameters. However, you can still use those parameters but netplan won't be able to roll-back the changes automatically.

If you instead run:

% netplan apply

This will generate configuration for the network backend and then apply those changes to the system immediately.

Changed in netplan:
status: New → Incomplete
Revision history for this message
carlos (nitrosito) wrote :

I check netplan try too. And not working for me. Bonding stays in default round-robind balancing. No 802.3ad.

Revision history for this message
Daniel Axtens (daxtens) wrote :

Netplan apply cannot change bond parameters either. You would either need to delete the bond and then run netplan apply, or just reboot. See LP: #1746419

Revision history for this message
carlos (nitrosito) wrote :

@Daniel in that case I guess it's a bug really.
I don't see normal to have to delete and restart.

I don't know if I tried that solution. But it does not seem normal to me. We can not use a tool in production that gives these problems, I hope they fix it

Revision history for this message
Daniel Axtens (daxtens) wrote :

I agree it is a bug. It is an unfortunate mix of netplan and systemd decisions/features/bugs causing the issue.

Do you mind if we mark this as a duplicate of LP: #1781203? It's the same root cause (netplan apply cannot change bond parameters) just with a different presentation (netplan try). Once we fix netplan apply, netplan try should work too.

Revision history for this message
Daniel Axtens (daxtens) wrote :

Sorry, I meant duplicate of LP: #1746419

Daniel Axtens (daxtens)
no longer affects: ubuntu
Revision history for this message
carlos (nitrosito) wrote :

OK, Thanks Daniel

carlos (nitrosito)
Changed in netplan:
status: Incomplete → Opinion
status: Opinion → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.