Also, there is no problem launching services manually after boot, and the issue doesn't happen on every boot, so whatever is happening is very time-dependant.
I can manually add a few seconds of delay to the boot process, but that feels hacky. -- 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/2081645 Title: (during boot) failed: Cannot assign requested address Status in systemd package in Ubuntu: Incomplete Bug description: Not sure where to post this, but since systemd controls boot precedence this section seems appropriate. I am testing oracular / 24.10 , and I bind some services to specific IPv6 addresses. In order to wait until the IP addresses are up before binding to them during boot, I use systemd-networkd-wait-online, modified to wait for IPv6. The problem is, despite systemd-networkd reporting the IPv6 addresses are up, binding to them still fails when the daemons attempt to launch. If I manually start the daemons after boot, they launch fine. It would appear the system is reporting IPv6 addresses as available before they are ready to be bound to by applications, therefore causing those application to fail during boot. Log attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
