Public bug reported:
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.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "journal-1.txt"
https://bugs.launchpad.net/bugs/2081645/+attachment/5820732/+files/journal-1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081645
Title:
(during boot) failed: Cannot assign requested address
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2081645/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
