On a fresh AWS instance I already see it stalling on package install, I do not even need to reboot :-/
ubuntu@ip-172-31-16-15:~$ sudo apt install linux-cloud-tools-common Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-cloud-tools-common 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 72.4 kB of archives. After this operation, 342 kB of additional disk space will be used. Get:1 http://eu-south-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 linux-cloud-tools-common all 5.15.0-25.25 [72.4 kB] Fetched 72.4 kB in 0s (632 kB/s) Selecting previously unselected package linux-cloud-tools-common. (Reading database ... 63666 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_5.15.0-25.25_all.deb ... Unpacking linux-cloud-tools-common (5.15.0-25.25) ... Setting up linux-cloud-tools-common (5.15.0-25.25) ... Created symlink /etc/systemd/system/multi-user.target.wants/hv-fcopy-daemon.service → /lib/systemd/system/hv-fcopy-daemon.service. Created symlink /etc/systemd/system/multi-user.target.wants/hv-kvp-daemon.service → /lib/systemd/system/hv-kvp-daemon.service. Created symlink /etc/systemd/system/multi-user.target.wants/hv-vss-daemon.service → /lib/systemd/system/hv-vss-daemon.service. Progress: [ 60%] [###################################################################################################..................................................................] < here it is hanging ~1 minute > Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. Processing triggers for man-db (2.10.2-1) ... Scanning processes... Scanning linux images... It is interesting that it even hits: Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142. That is the try to start it from: /var/lib/dpkg/info/linux-cloud-tools-common.postinst :63 Which has: deb-systemd-invoke $_dh_action 'hv-fcopy-daemon.service' 'hv-kvp-daemon.service' 'hv-vss-daemon.service' >/dev/null || true In Journal we can see the exact same time-out Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start timed out. Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: Timed out waiting for device /sys/devices/virtual/misc/vmbus!hv_kvp. Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: Dependency failed for Hyper-V KVP Protocol Daemon. Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: hv-kvp-daemon.service: Job hv-kvp-daemon.service/start failed with result 'dependency'. Apr 06 09:12:36 ip-172-31-16-15 systemd[1]: sys-devices-virtual-misc-vmbus\x21hv_kvp.device: Job sys-devices-virtual-misc-vmbus\x21hv_kvp.device/start failed with result 'timeout'. ** Summary changed: - Boot stall on non-azure systems due to linux-cloud-tools-common + Boot and package install/update stalled due to linux-cloud-tools-common (hv-kvp-daemon.service) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968013 Title: Boot and package install/update stalled due to linux-cloud-tools- common (hv-kvp-daemon.service) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
