[Bug 1990542] [NEW] initrd starts dhclient on interfaces that are not supposed to get an IP address

Launchpad Bug Tracker 1990542 at bugs.launchpad.net
Fri Sep 23 21:10:16 UTC 2022


You have been subscribed to a public bug by Dan Bungert (dbungert):

After trying several setups, I think this is a bug. If not - I can't
find how to fix things.

Setup: Ubuntu 22.04, with ubuntu-minimal installed (which depends on
isc-dhcp-client). A network with a bridge interface. This can be
anything, even an old /etc/network/interfaces file will do. For
simplicity, the following netplan setup is used:

network:
    version: 2
    ethernets:
        enp4s0:
          wakeonlan: true
            dhcp4: no
            dhcp6: no
    bridges:
      br0:
        interfaces: [enp4s0]
        dhcp4: yes
        dhcp6: yes
        parameters:
          stp: false
          forward-delay: 0


What happens:
Starting this machine will, during initrd phase, make dhclient fetch an IP address for enp4s0. Then netplan takes over and fetches an address for br0. If both enp4s0 and br0 have the same IP address from the DHCP-server, the machine will not be reachable.

What should happen:
enp4s0 should not get an IP address, as the netplan-configuration clearly says.

A workaround is to remove isc-dhcp-client (which, in turn, removes meta-
package ubuntu-minimal) and run update-initramfs -k all -u; afterwards,
the dhclient in initrd is (obviously) not there anymore.

** Affects: initramfs-tools (Ubuntu)
     Importance: Undecided
         Status: New

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

-- 
initrd starts dhclient on interfaces that are not supposed to get an IP address
https://bugs.launchpad.net/bugs/1990542
You received this bug notification because you are a member of Ubuntu Foundations Bugs, which is subscribed to the bug report.



More information about the foundations-bugs mailing list