Bionic: systemd: rename interface

Bug #1765463 reported by Thorsten
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

1) lsb_release -rd
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04

2) apt-cache policy systemd
systemd:
  Installed: 237-3ubuntu8

3) Kernel: linux-image-generic-hwe-16.04 4.15.0.17.18

/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""

/etc/systemd/netword/uplink0.link
[Match]
Path=pci-0000:02:00.0

[Link]
Name=uplink0

# update-initramfs -u

4) journalctl -b | grep rename
kernel: tg3 0000:02:00.1 eno2: renamed from eth1
kernel: tg3 0000:02:00.0 eno1: renamed from eth0

Tags: kernel networ
Thorsten (itopsatheg)
affects: linux-hwe-edge (Ubuntu) → systemd (Ubuntu)
Revision history for this message
Thorsten (itopsatheg) wrote :

systemd.network is working

cat /etc/systemd/network/uplink0.network
[Match]
Path=pci-0000:02:00.0
#Name=uplkink0

[Network]
DHCP=yes

networkctl status eno1
 Path: pci-0000:02:00.0

This was no solution:
cp /etc/systemd/netword/uplink0.link /lib/systemd/network/
update-initramfs -u

description: updated
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

/etc/systemd/netword/uplink0.link

that's invalid path, no?

/etc/systemd/network/ is the right path, and should work.

Changed in systemd (Ubuntu):
status: New → Invalid
Revision history for this message
Thorsten (itopsatheg) wrote :

typo

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

Can you please elaborate?

If one puts .link files in /etc/systemd/network, they should be copied into the initramfs, and they should results in the correct interface renames in the initramfs.

Once the typo was corrected (not sure if on the system, or it was in the bug description only), was everything working fine?

Or is it still a bug that .link files from /etc are not getting picked up into the initramfs for you?

Revision history for this message
Thorsten (itopsatheg) wrote :

the fault was somewhere else, this issue can be closed

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.