systemd-networkd-wait-online.service halts booting for 2 1/2 minutes

Bug #2060681 reported by Heinrich Schuchardt
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

When booting http://cdimage.ubuntu.com/ubuntu-server/daily-preinstalled/20240409/noble-preinstalled-server-riscv64.img.xz the system waits for 2 1/2 minutes for systemd-networkd-wait-online.service to time out.

See attached boot chart.
---
ProblemType: Bug
ApportVersion: 2.28.0-0ubuntu1
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20240409
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
DistroRelease: Ubuntu 24.04
Lspci-vt:
 -[0000:00]-+-00.0 Red Hat, Inc. QEMU PCIe Host bridge
            +-01.0 Red Hat, Inc. Virtio RNG
            \-02.0 Red Hat, Inc. Virtio block device
Lsusb: Error: command ['lsusb'] failed with exit code 1:
Lsusb-t:

Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
Package: systemd 255.4-1ubuntu7
PackageArchitecture: riscv64
ProcEnviron:
 LANG=C.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=vt220
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-20-generic root=LABEL=cloudimg-rootfs ro efi=debug earlycon init=/lib/systemd/systemd-bootchart
ProcVersionSignature: Ubuntu 6.8.0-20.20.1-generic 6.8.1
SystemdFailedUnits:
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
Tags: cloud-image noble
Uname: Linux 6.8.0-20-generic riscv64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
acpidump:

Revision history for this message
Heinrich Schuchardt (xypron) wrote :
affects: network-manager (Ubuntu) → systemd (Ubuntu)
tags: added: apport-collected cloud-image noble
description: updated
Revision history for this message
Heinrich Schuchardt (xypron) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Heinrich Schuchardt (xypron) wrote : Dependencies.txt

apport information

Revision history for this message
Heinrich Schuchardt (xypron) wrote : Lspci.txt

apport information

Revision history for this message
Heinrich Schuchardt (xypron) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Heinrich Schuchardt (xypron) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Heinrich Schuchardt (xypron) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Heinrich Schuchardt (xypron) wrote : ProcModules.txt

apport information

Revision history for this message
Heinrich Schuchardt (xypron) wrote : SystemdDelta.txt

apport information

Revision history for this message
Heinrich Schuchardt (xypron) wrote : UdevDb.txt

apport information

Revision history for this message
Nick Rosbrook (enr0n) wrote :

This is probably a duplicate of bug 2060311. Can you attach your netplan config?

Changed in systemd (Ubuntu):
status: New → Incomplete
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2060681

tags: added: iso-testing
Revision history for this message
Heinrich Schuchardt (xypron) wrote :

@Nick, thanks for picking this up.

/etc/netplan/ is empty on first boot. It is cloud-init that fills it with

$ sudo cat 50-cloud-init.yaml
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    ethernets:
        zz-all-en:
            dhcp4: true
            match:
                name: en*
            optional: true
        zz-all-eth:
            dhcp4: true
            match:
                name: eth*
            optional: true
    version: 2

The available interfaces are:

$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.15/24 metric 100 brd 10.0.2.255 scope global dynamic eth0
       valid_lft 86179sec preferred_lft 86179sec
    inet6 fec0::5054:ff:fe12:3456/64 scope site dynamic mngtmpaddr noprefixroute
       valid_lft 86182sec preferred_lft 14182sec
    inet6 fe80::5054:ff:fe12:3456/64 scope link
       valid_lft forever preferred_lft forever

Revision history for this message
Nick Rosbrook (enr0n) wrote :

Thanks. I am going to mark this as a duplicate. It does appear to be the same problem.

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.