Thanks for the update. I appreciate these things take time. Regards, /Arno
On Wed, 8 May 2019 at 16:21, Mathieu Trudel-Lapierre <mathieu...@gmail.com> wrote: > We're actively working on this. Fixing this bug had to wait for another > round of stable updates to complete while we correctly addressed the > problem and made sure it was fixed correctly. > > The fix is already in the git tree for netplan.io: > > https://github.com/CanonicalLtd/netplan/commit/d96a6a0f50c98301a36042f5065e7e834737122f > > The previous SRU round is finished, so now we'll do another that will > include this fix in priority, to land in 18.04, 18.10, 19.04 and eoan. > > This *does* take some time, SRUs need proper testing and a waiting > period in the -proposed component. Please help test the fix when it will > be available (another comment will follow saying so), this will greatly > help making it available at large as quickly as possible. > > ** Changed in: netplan > Status: New => Fix Committed > > ** Also affects: netplan.io (Ubuntu) > Importance: Undecided > Status: New > > ** Changed in: netplan.io (Ubuntu) > Status: New => In Progress > > ** Changed in: netplan.io (Ubuntu) > Importance: Undecided => Critical > > ** Changed in: netplan.io (Ubuntu) > Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) > > ** Description changed: > > + [Impact] > + Netplan users who need to bring up an interface (set its flag to IFF_UP) > but not define an address, using the networkd renderer, as the interface > may be further managed via another tool. > + > + [Test case] > + 1) Install Ubuntu > + 2) Set up netplan; with the following different use cases: > + > + == New VLAN == > + > + network: > + version: 2 > + renderer: networkd > + ethernets: > + [... whatever is already configured for the system...] > + vlans: > + vlan100: > + link: <the existing ethernet> > + id: 100 > + > + == Bring up an existing secondary interface == > + > + network: > + version: 2 > + renderer: networkd > + ethernets: > + eth0: {} > + > + > + 3) Verify that in both cases, the interface (ethernet or VLAN) is > brought up and shows UP, LOWER_UP flags in the output of 'ip link'. > + > + > + [Regression potential] > + As this brings a behavior change in netplan where as soon as an > interface is listed in the netplan YAML, it will be brought up, care should > be taken with existing configurations that do work, if specific devices are > listed but are not assigned an IP address, as they will be brought up by > networkd. This is expected to be a limited number of cases already, and > impact to network installations is minimal. > + > + > + ---- > + > The "manual" method in /etc/network/interfaces resulted in an interface > being brought up, but not having an IP address assigned. > > When configuring an Interface without an IP Address, netplan ignores the > interface instead of bringing it up. > > --- > network: > - version: 2 > - renderer: networkd > - ethernets: > - eth1: {} > + version: 2 > + renderer: networkd > + ethernets: > + eth1: {} > > Expected result from `netplan apply`: eth1 is brought up. > Actual result: eth1 is still down. > > Similarly `netplan generate` does not generate any file in > /run/systemd/network for eth1. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1763608 > > Title: > Netplan ignores Interfaces without IP Addresses > > Status in kolla: > Invalid > Status in netplan: > Fix Committed > Status in neutron: > Invalid > Status in netplan.io package in Ubuntu: > In Progress > > Bug description: > [Impact] > Netplan users who need to bring up an interface (set its flag to IFF_UP) > but not define an address, using the networkd renderer, as the interface > may be further managed via another tool. > > [Test case] > 1) Install Ubuntu > 2) Set up netplan; with the following different use cases: > > == New VLAN == > > network: > version: 2 > renderer: networkd > ethernets: > [... whatever is already configured for the system...] > vlans: > vlan100: > link: <the existing ethernet> > id: 100 > > == Bring up an existing secondary interface == > > network: > version: 2 > renderer: networkd > ethernets: > eth0: {} > > > 3) Verify that in both cases, the interface (ethernet or VLAN) is > brought up and shows UP, LOWER_UP flags in the output of 'ip link'. > > > [Regression potential] > As this brings a behavior change in netplan where as soon as an > interface is listed in the netplan YAML, it will be brought up, care should > be taken with existing configurations that do work, if specific devices are > listed but are not assigned an IP address, as they will be brought up by > networkd. This is expected to be a limited number of cases already, and > impact to network installations is minimal. > > > ---- > > The "manual" method in /etc/network/interfaces resulted in an > interface being brought up, but not having an IP address assigned. > > When configuring an Interface without an IP Address, netplan ignores > the interface instead of bringing it up. > > --- > network: > version: 2 > renderer: networkd > ethernets: > eth1: {} > > Expected result from `netplan apply`: eth1 is brought up. > Actual result: eth1 is still down. > > Similarly `netplan generate` does not generate any file in > /run/systemd/network for eth1. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/kolla/+bug/1763608/+subscriptions > -- Arno van Huyssteen Director Field Engineering EMEA APAC Service Provider Cloud & Edge +32 485 077 777 | arno.van.huysst...@canonical.com #economicsmatter <https://drive.google.com/file/d/1iJbM5gR6PhHIpGWvPvgcKJL4FlEollR6/view?usp=sharing> #infrastructureascode #edge #ubuntu #canonical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763608 Title: Netplan ignores Interfaces without IP Addresses To manage notifications about this bug go to: https://bugs.launchpad.net/kolla/+bug/1763608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
