Here is an example netplan yaml that emulates this configuration in a
test container.

network:
    version: 2
    ethernets:
        eth0:
            dhcp4: false
    bonds:
        bond0:
            interfaces: [eth0]
            parameters:
                mode: active-backup
                arp-interval: 10
    vlans:
        bond0.100:
            id: 100
            link: bond0
            addresses: [10.44.49.39/24]
            routes:
              - to: 0.0.0.0/0
                via: 10.44.49.1

Setting 'arp-interval' causes the link to drop after a short period
because the lxd bridge for the container isn't configured compatibly; so
I've removed that line for testing here.

However, I haven't understood why you have addresses assigned on both
the bond and the vlan, or what you're intending to achieve by
reconfiguring the bond with nmcli.  Here, the links appear to work as
expected when managed directly with iproute2.

# ip -4 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
3: bond0.100@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
state UP group default qlen 1000
    inet 10.44.49.39/24 brd 10.44.49.255 scope global bond0.100
       valid_lft forever preferred_lft forever
# ip link set dev bond0 down
# ip -4 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
# ip link set dev bond0 up
# ip -4 addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
3: bond0.100@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
state UP group default qlen 1000
    inet 10.44.49.39/24 brd 10.44.49.255 scope global bond0.100
       valid_lft forever preferred_lft forever
#

I don't see anything here to indicate the kernel is mishandling these
interfaces.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1790098

Title:
  vlan created on bond fails auto activation on updating parent network
  bond

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Auto activation of Vlan created over network-bond fails if bond is 
deactivated and reactivated.
   
  Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar 
Deshpande(manda...@in.ibm.com) 
   
  ---uname output---
  Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Created a network bond with static IP address (and no IPv6 address); 
active backup mode; ARP polling; single slave.

  2. Created a VLAN using said network bond with static IPv4 address
  (and no IPv6 address).

  3. Can ping from the appliance to a target on both links (the parent
  bond and the VLAN).

  4. Switched to another slave for the created bond

  5. Can still ping from the appliance to a target via the parent bond;
  however, cannot ping to the target via the VLAN.

  =============================================================================
  Detailed steps:

  1. Initial setup:
  ============
  root@S36MANDAR:~# nmcli c s
  NAME                UUID                                  TYPE      DEVICE  
  enc1a80             c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00             2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  enc1d40             ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --      

  2. Create Netwrok-bond with one slave:
  ================================
  root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 
ipv4.method disabled ipv6.method ignore
  Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully 
added.

  root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1
  Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) 
successfully added.
  root@S36MANDAR:~# nmcli con up bond-slave-enc1d40
  Connection successfully activated (D-Bus active path: 
/org/freedesktop/NetworkManager/ActiveConnection/18)
  root@S36MANDAR:~# nmcli c s
  NAME                UUID                                  TYPE      DEVICE  
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40 
  enc1a80             c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc8f00             2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1             4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond      mybond1 
  enc1d40             ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --      

  3. Create vlan over mybond1:
  =======================
  root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname 
vlanbond.100 dev mybond1 id 100  ipv4.method disabled ipv6.method ignore
  Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully 
added.
  root@S36MANDAR:~# nmcli c s
  NAME                UUID                                  TYPE      DEVICE    
   
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40   
   
  enc1a80             c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80   
   
  enc8f00             2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00   
   
  mybond1             4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond      mybond1   
   
  vlanbond.100        e054df42-97a0-492b-b2c9-b9571077493e  vlan      
vlanbond.100 
  enc1d40             ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --        
   

  4. Reactivate bond : 
  =================
  root@S36MANDAR:~# nmcli con up mybond1
  Connection successfully activated (master waiting for slaves) (D-Bus active 
path: /org/freedesktop/NetworkManager/ActiveConnection/30)

  root@S36MANDAR:~# nmcli c s
  NAME                UUID                                  TYPE      DEVICE  
  enc1a80             c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80 
  enc1d40             ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  enc1d40 
  enc8f00             2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00 
  mybond1             4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond      mybond1 
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  --      
  encw1810            4ddeb38e-d5f7-3814-abb7-be50b8da874e  ethernet  --      
  vlanbond.100        e054df42-97a0-492b-b2c9-b9571077493e  vlan      --      

  As is seen, vlan(vlanbond.100) did not get activated

  Now, if manually I make vlan connection up, it gets activated:

  root@S36MANDAR:~# nmcli  con up vlanbond.100
  NAME                UUID                                  TYPE      DEVICE    
   
  bond-slave-enc1d40  cfe4b245-3dda-4f45-b7b4-6d40d144a02f  ethernet  enc1d40   
   
  enc1a80             c3a2037d-60a3-3cb4-9234-45aed55f7093  ethernet  enc1a80   
   
  enc8f00             2423add6-1464-3765-877c-a214dc497492  ethernet  enc8f00   
   
  mybond1             4b918a65-43a6-4ec3-b3c4-388ed52b116d  bond      mybond1   
   
  vlanbond.100        e054df42-97a0-492b-b2c9-b9571077493e  vlan      
vlanbond.100 
  enc1d40             ff2d70f8-130e-3dc6-ab24-1dba07563605  ethernet  --        
   
  encw1810            4ddeb38e-d5f7-3814-abb7-be50b8da874e  ethernet  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790098/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to