-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
network configuration failed on reboot #17012
Comments
This is already fixed by 628f08b. @keszybz Please backport the commit to v245 (and maybe older) -stable branch.
I am not sure, but I hope this is already fixed by #16982. I will check it. |
The issue seems already fixed by PR systemd#16982 and its follow-up commit 4934ba2.
|
(Also 48d0248 needs to be backported to v244 or older -stable repository.) |
The issue seems already fixed by PR systemd#16982 and its follow-up commit 4934ba2. (cherry picked from commit 766f8f3)
The issue seems already fixed by PR systemd#16982 and its follow-up commit 4934ba2.
The issue seems already fixed by PR systemd#16982 and its follow-up commit 4934ba2.
|
is there any chance getting the fix included in current LTS version (Ubuntu 20.04) |
|
@deepika-maj Please contact Ubuntu's support forum to backport the fix. Ubuntu 20.04 seems to use v245, which is too old to discuss the issue here. |
systemd version the issue has been seen with
Used distribution
Issue details
I configured 255 IPv4 address (including primary IP) using netplan but when the server restart, it time out on configuring the interface. If I limit total IPv4 addresses to 181 or less, it works. But anything larger than 181 fails.
Below are my configurations and error logs.
/etc/netplan/10-ens3.yaml
The above config works if I run
netplan applybut when I reboot, it does not work.networkctl
/etc/systemd/system/systemd-networkd.service.d/override.conf
systemctl status systemd-networkd.service
journalctl -b -u systemd-networkd
The text was updated successfully, but these errors were encountered: