Comment 8 for bug 1745597

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Verification-done on xenial: nplan 0.32~16.04.5
Verification-done on artful: nplan 0.32~17.10.4

With the updated nplan; the mii-monitor-interval set in configuration is correctly applied to the device as expected, and is processed as milliseconds or seconds, as appropriate to the config:

676 --> 676
676ms --> 676
1s --> 1000

ubuntu@warm-sole:~$ cat /sys/class/net/bond0/bonding/miimon
1000
ubuntu@warm-sole:~$ cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    version: 2
    ethernets:
        ens6:
            match:
                macaddress: 52:54:00:5c:36:55
            mtu: 1500
            set-name: ens6
        ens7:
            match:
                macaddress: 52:54:00:ca:e3:8e
            mtu: 1500
            set-name: ens7
    bonds:
        bond0:
            interfaces: [ ens6, ens7 ]
            addresses:
            - 10.3.99.17/24
            gateway4: 10.3.99.1
            parameters:
                mii-monitor-interval: 1s