[Bug 1988657] [NEW] VLAN gets IP address assignment from parent device when using "match macaddress"

[Marvin Glenn]

Public bug reported:

System is Ubuntu 18.04 with Netplan 0.99-0ubuntu3~18.04.5(amd64)

When using the "match macaddress" mechanism to guarantee the assignment
of the ethernet device name to a particular port, VLANs added to that
device will not get the the IP addresses assigned to them but rather the
IP address of the parent ethernet device.

In the example below from my system, the 'l2club' VLAN would get the
192.168.2.1 address, along with eno1 receiving it.  The address
10.232.228.16 was not assigned to anything.  With the "match macaddress"
section was removed, both interfaces would then get the IP addresses
that were expected.

network:
  version: 2
  renderer: networkd
  ethernets:
    eno1:
      match:
        macaddress: 00:24:e8:00:00:00
      addresses:
        - 192.168.2.1/24
  vlans:
    l2club:
      id: 10
      link: eno1
      addresses:
        - 10.232.228.16/8

** Affects: netplan
     Importance: Undecided
         Status: New

** Affects: netplan.io (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to netplan.io in Ubuntu.
Matching subscriptions: foundations-bugs
https://bugs.launchpad.net/bugs/1988657

Title:
  VLAN gets IP address assignment from parent device when using "match
  macaddress"

Status in netplan:
  New
Status in netplan.io package in Ubuntu:
  New

Bug description:
  System is Ubuntu 18.04 with Netplan 0.99-0ubuntu3~18.04.5(amd64)

  When using the "match macaddress" mechanism to guarantee the
  assignment of the ethernet device name to a particular port, VLANs
  added to that device will not get the the IP addresses assigned to
  them but rather the IP address of the parent ethernet device.

  In the example below from my system, the 'l2club' VLAN would get the
  192.168.2.1 address, along with eno1 receiving it.  The address
  10.232.228.16 was not assigned to anything.  With the "match
  macaddress" section was removed, both interfaces would then get the IP
  addresses that were expected.

  network:
    version: 2
    renderer: networkd
    ethernets:
      eno1:
        match:
          macaddress: 00:24:e8:00:00:00
        addresses:
          - 192.168.2.1/24
    vlans:
      l2club:
        id: 10
        link: eno1
        addresses:
          - 10.232.228.16/8

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1988657/+subscriptions