This issue is fixed in Jammy, but not earlier LTS releases.
--
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/1928733
Title:
Starting systemd Network Service fails with "Inva
What version is this fix in please? Just asking as i was reported back
in May 2021. Thanks.
--
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/1928733
Title:
Starting systemd
Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: systemd (Ubuntu Impish)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
per comment 6, this should be fixed in jammy, so marking fixed released
there.
** Changed in: systemd (Ubuntu)
Status: Triaged => 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://
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.
** Changed in: systemd (Ubuntu Hirsute)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
> If I understand correctly the fix will go in the latest Bionic
packages?
I think it's very unlikely that the very recent, and rather large,
patchset will get backported back to the relatively old and much
different codebase in bionic. I haven't looked at it in detail yet
though.
--
You receive
Hi Dan,
Thank you for that. The server is bare metal, not in a container.
If I understand correctly the fix will go in the latest Bionic packages?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bu
ok it looks like this *might* be upstream bug 16156, which unfortunately
was just very recently fixed, so backporting that to bionic may be
difficult.
I'll mark the bug and take a look but even if it is possible to backport
the fix, it will likely take a while.
** Changed in: systemd (Ubuntu)
marking wontfix for groovy, as a backport of this size is unlikely to
happen before groovy reaches end of life this month.
** Changed in: systemd (Ubuntu Hirsute)
Status: New => Triaged
** Changed in: systemd (Ubuntu Focal)
Status: New => Triaged
** Changed in: systemd (Ubuntu Bion
it looks like you're seeing this problem inside an lxc/lxd container,
not on bare metal, is that correct?
--
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/1928733
Title:
Sta
Would there be any update on this please?
--
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/1928733
Title:
Starting systemd Network Service fails with "Invalid argument"
Sta
Hi Dan, thanks for that. Interestingly it was much harder to reproduce
the problem with debugging enabled, but we got it on about the 15th try.
The log is attached.
** Attachment added: "systemd-networkd-1.log"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1928733/+attachment/5498612
can you turn on systemd debug (e.g. with systemd.log_level=debug boot
parameter) and reproduce the error, then check the logs for additional
messages indicating what the failure is
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
13 matches
Mail list logo
