[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Clarifying what worked for me across all the servers where I need this config: cat

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Is it possible this regressed sometime between Bionic and Focal? I am observing this in 20.04. Early in dmesg I see my interface renamed from eth1 to eno2, then my netplan attempts to rename with a match (on name=eno2) to my desired name ("ceph" in this case). I see syslog message:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

For what it's worth, I'm still seeing set-name having no affect on a server's only interface. Server is using Ubuntu 19.04, with netplan.io-0.96-0ubuntu4.1, AMD64 arch. It's a bare-metal server with a single "e1000e" ethernet device. No cloud-init installed. Config file

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3 --- netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium * debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert commit ebc212a: make renderer values explicit at the end of each parsing

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4 --- netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium * debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert commit ebc212a: make renderer values explicit at the end of each parsing

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Still verification-done on bionic and cosmic; this hasn't changed with the new revision in -proposed. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.04.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.10.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

A possible SRU regression has been reported against netplan.io 0.96-0ubuntu0.18.10.2 in LP: #1825206. This version has been rolled back to -proposed while the investigation is ongoing. ** Changed in: netplan.io (Ubuntu Cosmic) Status: Fix Released => Fix Committed -- You received this

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.2 --- netplan.io (0.96-0ubuntu0.18.10.2) cosmic; urgency=medium * d/p/0001-Partially-revert-the-change-for-enabling-systemd-net.patch: Partially revert changes to networkd jobs ordering: leave systemd-networkd

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This does not need re-testing, already in bionic/cosmic, just closed again due to changelog for this big backport. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.04.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

No need to re-test these; it's already been included in bionic/cosmic and bug comments are a side-effect of the changelogs for the upload with this backport. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

no need to re-test this on bionic/cosmic ** Changed in: netplan.io (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Changed in: netplan.io (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Tags removed: verification-needed verification-needed-bionic

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.96-0ubuntu0.18.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This bug was fixed in the package netplan.io - 0.40.1~18.04.3 --- netplan.io (0.40.1~18.04.3) bionic; urgency=medium * Fix idempotency in renaming: bond members should be exempt from rename, as they may all share a single MAC for the bond device. (LP: #1802322) *

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This bug was fixed in the package netplan.io - 0.40.2.2 --- netplan.io (0.40.2.2) cosmic; urgency=medium * Fix idempotency in renaming: bond members should be exempt from rename, as they may all share a single MAC for the bond device. (LP: #1802322) * tests/integration.py:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Resetting the tags to verification-done as per the discussion above. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.40.2.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

The SRU has been rolled back while the fix for the regression is being prepared. I still consider the previous SRU verification valid so am resetting the bug state but not the tags. ** Changed in: netplan.io (Ubuntu Bionic) Status: Fix Released => Fix Committed ** Changed in: netplan.io

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This change introduces a regression: calling netplan apply is not idempotent for bonds, see https://bugs.launchpad.net/netplan/+bug/1802322 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This bug was fixed in the package netplan.io - 0.40.2.1 --- netplan.io (0.40.2.1) cosmic; urgency=medium * Fix typo breaking rename on 'netplan apply'. (LP: #1770082) -- Mathieu Trudel-Lapierre Mon, 22 Oct 2018 14:58:40 -0400 ** Changed in: netplan.io (Ubuntu Cosmic)

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

@Mathieu: Me and Nicorac have the same bug: if set-name is used, there will be no IP at boot. The bug 1768827 is about the same problem as this one (set-name not renaming interface at boot), which is resolved by now... The strange thing is the inconsistency between the two installation types

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This bug was fixed in the package netplan.io - 0.40.1~18.04.2 --- netplan.io (0.40.1~18.04.2) bionic; urgency=medium * Fix typo breaking rename on 'netplan apply'. (LP: #1770082) netplan.io (0.40.1~18.04.1) bionic; urgency=medium * Backport netplan 0.40.1 to 18.04. (LP:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

@Marcos: Please file a new bug for your own issue; include the output of 'networkctl', and report the bug number here so we can find it. >From a quick look, I think there's no carrier detected. This could be a driver bug. -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Please use bug 1768827 to track such "no IP at boot" issues; there's nothing that currently indicates that this is a regression, it needs further investigation, but not here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

@Nicorac: Tested with static IP and had same result. ubuntu@ubuntu:~$ cat /etc/netplan/01-netcfg.yaml # This file describes the network interfaces available on your system # For more information, see netplan(5). network: version: 2 renderer: networkd ethernets: eth0: match:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

@Mathieu: I reinstalled my Virtualbox VM (using the ubuntu-18.04-server- amd64.iso image) and tested again and the result was the same. netplan config: ubuntu@ubuntu:~$ cat /etc/netplan/01-netcfg.yaml # This file describes the network interfaces available on your system # For more information,

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

@Marcos,#80: ubuntu-18.04-server-amd64.iso is exactly the ISO I'm using for my installations. @Mathieu,#82: you've removed the verification-failed-bionic tag but 0.40.1~18.04.2 is still not working on my side, both on VirtualBox VM and on Proxmox VM (KDE). Interface renaming works but IP

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Yes, that's because it doesn't appear like the issues you have are a regression caused by the updates, and we don't know what's wrong. You have a bug open for your issue, and we still need to figure out what doesn't work there. -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Verification-done on bionic with netplan.io 0.40.1~18.04.2: Using the following config: network: version: 2 ethernets: maas0: addresses: - 10.3.21.29/20 gateway4: 10.3.16.1 match: macaddress: 52:54:00:4d:3e:84

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Verification-done for cosmic using netplan.io 0.40.2.1: I have verified that renames happen correctly with the config provided in test cases and the config I have shown for the testing on bionic. In all cases, set-name is applied as the new name for the interface, as expected. On reboot, this is

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

** Description changed: [Impact] Systems relying on renaming network interfaces at boot and when 'netplan apply' is run. [Test case] - Write a new netplan YAML (adjusting for current system as necessary): network: version: 2 ethernets: ens3:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This bug was fixed in the package netplan.io - 0.40.2.1 --- netplan.io (0.40.2.1) cosmic; urgency=medium * Fix typo breaking rename on 'netplan apply'. (LP: #1770082) -- Mathieu Trudel-Lapierre Mon, 22 Oct 2018 14:58:40 -0400 ** Changed in: netplan.io (Ubuntu) Status:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Tested just now... It is working for the subiquity installer version (ubuntu-18.04-live-server-amd64.iso) but it does not apply ip address on boot if installed with the debian-intaller version (ubuntu-18.04-server- amd64.iso). -- You received this bug notification because you are a member of

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Still not working on my side (plain vanilla Ubuntu Server 18.04, fully updated, no cloud). The renaming regression of 0.40.1~18.04.1 has been fixed, but it's still not applying IP address just after boot. A manual "netplan apply" correctly configures the network interface.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.40.2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.40.1~18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

I found time to run more tests and discovered that my patches were wrong... And the fix was actually even simpler. root@netplan:~# cat fix-bug-1770082.diff Index: b/netplan/cli/commands/apply.py === ---

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

IMHO if a "match" option is present (especially with a MAC condition), it should always override the ID. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Actually, sent the wrong patch... this is the right one: root@netplan:~# cat fix-bug-1770082.diff --- a/netplan/cli/commands/apply.py +++ b/netplan/cli/commands/apply.py @@ -170,15 +170,15 @@ link = netifaces.ifaddresses(interface)[netifaces.AF_LINK][0] macaddress =

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

After some debugging, I could make it work... I'm not a programmer, so it might be wrong, but it's working: root@netplan:~# cat fix-bug-1770082.diff --- a/netplan/cli/commands/apply.py +++ b/netplan/cli/commands/apply.py @@ -170,15 +170,15 @@ link =

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Ok, I also re-read Daniel's comment and I see that he mentioned it working on the previous upload. This really seems like a regression - for the time being let's mark this verification-failed-bionic so that no one accidentally releases it to -updates. ** Tags removed: verification-done-bionic **

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Just confirmed the regression... It's working as expected on boot, but is renaming to the "ID" key, instead of the "set-name" when live. E.g. if we have: ens0p3: match: macaddress: 01:02:03:04:05:06 set-name: eth0 It will be renamed to ens0p3 on netplan apply. eth0: match:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

So the bug here is about renaming interfaces on boot and this seems to be resolved by the new upload. Does this regress previous behavior? Did renaming interfaces on a running system work in the previous version and this upload introduces a regression? If not, we should fill in a separate bug and

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hi, This works on reboot but not so well after the system boots. Say I have the following file: network: version: 2 ethernets: ens7: dhcp4: true match: macaddress: 52:54:00:b4:02:6e set-name: myif1 optional: true

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Resetting to verification-done for bionic; using netplan.io 0.40.1~18.04.1: I have run more tests and I can verify that renames at boot are behaving correctly with netplan -- netplan follows exactly the configuration provided on the system: network: version: 2 ethernets: ens6:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Wrong cut: --- # dpkg -s netplan.io | grep Version Version: 0.40.1~18.04.1 --- -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Sorry, still not working here. Same behavior as my previous post. Maybe it's due to VirtualBox? Haven't tried on my production KDE (Proxmox) yet... --- # dpkg -s netplan.io | grep Version Version: 0.40~18.04.1 --- ** Tags removed: verification-needed-bionic ** Tags

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.40.1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Sorry for being such a buzzkill, but it's still not working on my side :( = Reinstalled 18.04.1 server x64 from scratch in a clean VirtualBox VM. = #

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.40~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

I've tried some workarounds: - kernel parameter "net.ifnames=0" on kernel commandline: NOT WORKING - ebtables: NOT WORKING - add "@reboot /usr/sbin/netplan apply" to root cron: NOT WORKING The following works on my side: * create a new unit file: /etc/systemd/system/netplan-workaround.service

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

@Marcos: ebtables is ininfluent on my side. It is installed with server version and the bug persists both with and without it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Just tried with a fresh installed Ubuntu SERVER 18.04.1. The interface now got renamed but IP address is not applied, both static and DHCP. If I run "netplan apply" just after reboot+login, network interface is configured correctly (again, both with static/DHCP address).

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Nicorac, I misread your message, what I meant to say is that installing ebtables makes netplan to work properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1770082

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Yes... I tried multiple times on VirtualBox. Installed from mini.iso without selecting anything, then edited /etc/netplan/01-netcfs.yaml, added match macaddress and set-name statements, rebooted and no luck. Then installed ebtables and rebooted and it worked, then uninstalled ebtables and it

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Do you mean that removing ebtables (if possible) let rename work properly? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Can't edit, so I'm writing another message. I was wrong about ubuntu- desktop, it does not install ebtables by default, but server does. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This problem still exists in a fresh (minimal) installation of Ubuntu 18.04. To reproduce, just install from mini.iso without selecting any packages at tasksel. I've discovered that if you install ebtables it works as expected. That's why it works if you select an Desktop or Server option at

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

** Changed in: netplan Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not renaming devices on

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Since the new issue is tracked in a separate bug and currently only reproducible by the reporter, I am releasing the current update as is. In case this indeed turns out to be a regression, let's consider fixing it with a subsequent upload. -- You received this bug notification because you are a

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This bug was fixed in the package nplan - 0.32~16.04.6 --- nplan (0.32~16.04.6) xenial; urgency=medium [ Mathieu Trudel-Lapierre ] * tests/integration.py: Fix autopkgtests involving bonds/bridges to do proper cleanup every time, so later tests don't unnecessarily wait for an

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This bug was fixed in the package netplan.io - 0.36.3 --- netplan.io (0.36.3) bionic; urgency=medium * Generate udev rules files to rename devices (LP: #1770082) Due to a systemd issue[1], using link files to rename interfaces doesn't work as expected. Link files will not

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

The behavior is not reproducible, maybe a race condition? I'm actually not getting IP addres for static interface too :-( I agree, let's continue there: https://bugs.launchpad.net/netplan/+bug/1768827 -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

I'd be a bit surprised if there really was a regression due to the change, we're more likely seeing something going down due to the DHCP server being slow to respond, possibly because it already responded before? What does the 'networkctl' command show immediately after boot? Let's continue

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Sorry for the confusion. Current version (0.36.2): - both devices not renamed after boot (have original enp.. names) - static and dynamic IPs correctly assigned Proposed version (0.36.3): - both devices correctly renamed after boot: :91 gets renamed eth_static :f5 gets renamed to eth_dhcp -

Re: [Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hi, I'm a bit confused then. This is the netplan config you mentioned: network: version: 2 renderer: networkd ethernets: id0: match: macaddress: 08:00:27:6b:d8:91 set-name: eth_static addresses: [ 1.2.3.4/16 ] gateway4: 5.6.7.8 id1: match:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

@Daniel: no, it's a regression to me because set-name never worked and now DHCP stopped working too. But I'm not testing the same environment as you, I'm on VirtualBox and this is my original bug report (linked to this one): https://bugs.launchpad.net/netplan/+bug/1768827 -- You received this

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hi, I have confirmed that the Bionic package works on the cloud service where the bug was originally observed. With this package, the affected migrations now succeed. Regards, Daniel -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hi, I can verify correct behaviour with renaming, static IPs and DHCP with KVM. I'm about to check some cloud services as well. Nicorac, are you claiming this is a regression or just an incomplete fix? If it's just an incomplete fix, I think we should spin that out into another bug and fix it

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

** Tags removed: verification-failed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1770082 Title: systemd-networkd not

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Partially working here on fully updated Ubuntu 18.04 Server on VirtualBox :( I've enabled -proposed repo and updated both nplan/bionic-proposed and netplan.ion/bionic-proposed packages. Now interfaces got renamed, but IPs are not assigned at boot (both DHCP and static ones). Calling "netplan

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted netplan.io into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/netplan.io/0.36.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hi Łukasz, I couldn't find the package in -proposed, but I was able to download it from the link. I verified that a device was not renamed with 0.32~16.04.5 but was correctly renamed with 0.32~16.04.6, so for Xenial, verification succeeds. Regards, Daniel ** Tags removed:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Hello Daniel, or anyone else affected, Accepted nplan into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nplan/0.32~16.04.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

** Description changed: + [Impact] + Systems relying on renaming network interfaces at boot and when 'netplan apply' is run. + + [Test case] + - Write a new netplan YAML (adjusting for current system as necessary): + network: + version: 2 + ethernets: + ens3: +

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Could this bug be updated with SRU relevant information? Also, it would also be nice if we had the same changes prepared for netplan.io in bionic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Thanks for the update. Referring to this duplicate bug (https://bugs.launchpad.net/netplan/+bug/1768827), is it going to be backported to 18.04? Or is there a way to install 0.38 on Ubuntu Server 18.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

** Also affects: nplan (Ubuntu) Importance: Undecided Status: New ** Changed in: nplan (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

This bug was fixed in the package netplan.io - 0.38 --- netplan.io (0.38) cosmic; urgency=medium * New upstream release: - Write udev .rules files to /run/udev/rules.d to enforce interface renaming. (LP: #1770082) - Don't traceback for 'netplan ip leases' when iface

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

** Also affects: netplan.io (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan.io (Ubuntu) Status: New => In Progress ** Changed in: netplan.io (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification

Re: [Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

"This is why I added cloud-init to affected packages -- cloud-init should not be second- guessing the network layer and attempting to do renames / to run" There is no second guessing. In the case where we have no network config, there is no renaming; we accept whatever name is given. If the

Re: [Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

On Fri, May 25, 2018 at 9:09 AM, Mathieu Trudel-Lapierre wrote: > I'm not completely sure where the code lives in cloud-init; it looks a > bit like what's in: > > cloudinit/net/netplan.py > > But the code does read as though it should not be running 'udevadm test- > builtin

Re: [Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

On Fri, May 25, 2018 at 8:48 AM, Mathieu Trudel-Lapierre wrote: > My recommended course of action for cosmic: > > - drop udevadm (net_setup_link) call from cloud-init This will still be needed in the case that we have a network config with names. Cloud-init runs after udev

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

My recommended course of action for SRUs: - write udev .rules files from netplan to enforce renaming - drop udevadm (net_setup_link) call from cloud-init The above should be sufficient and non-intrusive enough for SRU. The tasks for cosmic are additional changes to clean up the behavior for

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

I'm not completely sure where the code lives in cloud-init; it looks a bit like what's in: cloudinit/net/netplan.py But the code does read as though it should not be running 'udevadm test- builtin net_setup_link'. However, deploying a system with MAAS shows a

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

** Patch added: "draft systemd patch to skip should_rename(), adds extra debug info" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1770082/+attachment/5144272/+files/debug.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

My recommended course of action for cosmic: - drop udevadm (net_setup_link) call from cloud-init - drop set-name "renaming" from cloud-init / maas - drop replug code in netplan; replace with proper .link code, possibly call to net_setup_link. - maybe write udev rule for renaming in netplan

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

netplan changes are available in git: Daniel's patch to write udev rules (SRU material): https://github.com/CanonicalLtd/netplan/commit/b0c51bfa8ba8b898a9feaed9cd7d8790d147d35d Daniel's patch + dropping replug code + rework 'netplan apply' (code for cosmic); in progress for upload to cosmic:

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: netplan Status: Incomplete => Confirmed ** Changed in: cloud-init (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

There are a couple of pieces in play here. One aspect is that we don't really want to write the .link files for systemd-networkd to /lib or get anything from /run into the initrd -- that defeats the purpose of netplan's config being dynamic. The second aspect is that depending on how the systems

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

That's not the final conclusion; the issue is still being discussed upstream; in particular as to why only the interface name cannot be modified at runtime by .link files. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

As discussed on https://github.com/systemd/systemd/issues/9006 The initrd (!) should have NamePolicy=kernel in /lib/systemd/network/99-default.link -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

Re: [Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

We really only want to be allowed to rename interfaces that have requested it. This means other interfaces which do not have a set-name directive will have the kernel name. On Thu, May 24, 2018 at 6:56 AM, Mike Jonkmans <1770...@bugs.launchpad.net> wrote: > Things seem to work when i change the

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

Things seem to work when i change the NamePolicy in the initrd file /lib/systemd/network/99-default.link to `NamePolicy=kernel` Leaving out the other NamePolicy-options, prevents renaming in the initrd fase. Which allows later renames from .link files/netplan. -- You received this bug

  1   2   >