This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
The release of this SRU has been rolled back in jammy because of bug
#2035406 which appears to be a regression introduced in the new version
of systemd.
** Changed in: systemd (Ubuntu Jammy)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of
This bug was fixed in the package systemd - 249.11-0ubuntu3.10
---
systemd (249.11-0ubuntu3.10) jammy; urgency=medium
[ Nick Rosbrook ]
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 252.5-2ubuntu3.1
---
systemd (252.5-2ubuntu3.1) lunar; urgency=medium
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
This bug was fixed in the package systemd - 253.5-1ubuntu4
---
systemd (253.5-1ubuntu4) mantic; urgency=medium
* Revert "Drop Provides: time-daemon for bin:systemd-timesyncd"
File: debian/control
I have verified the fix on Jammy using systemd 249.11-0ubuntu3.10 from
jammy-proposed:
root@clean-jammy-amd64:/home/nr# apt-cache policy systemd
systemd:
Installed: 249.11-0ubuntu3.10
Candidate: 249.11-0ubuntu3.10
Version table:
*** 249.11-0ubuntu3.10 500
500
I have verified the fix on Lunar using systemd 252.5-2ubuntu3.1 from
lunar-proposed:
root@clean-lunar-amd64:/home/nr# apt-cache policy systemd
systemd:
Installed: 252.5-2ubuntu3.1
Candidate: 252.5-2ubuntu3.1
Version table:
*** 252.5-2ubuntu3.1 500
500
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Jammy)
Status: New => Triaged
** Changed in: systemd (Ubuntu Lunar)
Status: New =>
** Tags added: systemd-sru-next
--
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/2009743
Title:
networkd: classless routes served by DHCP are created incorrectly
Status in
** Changed in: systemd
Status: New => Fix Released
--
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/2009743
Title:
networkd: classless routes served by DHCP are
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
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/2009743
Title:
networkd: classless routes served by DHCP are
** Changed in: systemd
Status: Unknown => New
--
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/2009743
Title:
networkd: classless routes served by DHCP are created
** Bug watch added: github.com/systemd/systemd/issues #28280
https://github.com/systemd/systemd/issues/28280
** Also affects: systemd via
https://github.com/systemd/systemd/issues/28280
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
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/2009743
Title:
networkd: classless routes served by DHCP
I forgot to say, the above was after updating systemd to
249.11-0ubuntu3.9
--
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/2009743
Title:
networkd: classless routes served
Here is the requested log. The sequence of operations was:
sudo systemctl restart systemd-networkd
sudo networkctl forcerenew bond0
Sylvain's diagnostic seems to have hit the nail on the head. I see the
following messages in the log:
bond0: DHCP: requested route destination 10.88.88.0/24 is in
Hi Pedro,
Can you please try this with the latest version of systemd? We have
249.11-0ubuntu3.9 which has a patch for a similar sounding bug (I don't
*think* it's the same thing, but just to be sure).
Assuming that does not resolve the issue, can you please provide debug-
level logs from
Yes I can confirm the classless routes we are trying to serve are under
the main subnet:
10.0.0.0/8 dev enp24s0
10.88.88.0/24 via 10.10.1.2 dev enp24s0
10.96.0.0/11 via 10.10.1.2 dev enp24s0
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I have the same issue.
I may be wrong, but it seem to me that it's related to the following DHCP
options :
DHCP option 1 : [SubnetMask]
DHCP option 121 : classless static route [DestCIDR] [Gateway]
When DestCIDR is within the subnet, the gateway is dropped by systemd-networkd
: the route is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
20 matches
Mail list logo
