This bug was fixed in the package systemd - 237-3ubuntu10.56
---
systemd (237-3ubuntu10.56) bionic-security; urgency=medium
* debian/udev.preinst:
Add check_ID_NET_DRIVER() to ensure that on upgrade or install
from an earlier version ID_NET_DRIVER is present on network
Attached is an improvement on the previous patch revision. Output is now
forwarded to logger, we use shell expansion to enumerate network
devices, we omit loopback, and we added a udevadm settle to wait for any
thunderstorms to resolve before we continue installing the new udev
package.
** Patch
Attached is the second patch required to fully fix this bug. It adds a
check on preinstall to see if ID_NET_DRIVER is present on the network
interface, and if it is missing, call udevadm trigger -c add on the
interface to add it.
** Patch added: "Debdiff for systemd on Bionic part two"
Thank to Microsoft for fixing the issue on all AKS clusters.
But for the history we fixed that by just cordoning and then draining all
cordoned nodes.
It effectively gracefully rotates the node pools.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
We got bite by this but we added a cron to our 18.04 instances:
* * * * * host google.com || dhclient
works-for-us :-)
HTH,
Norberto
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
The failure mode still exists if "udevadm trigger" has been issued
before the package upgrade to systemd 237-3ubuntu10.55.
That is, if unattended-upgrades or the user had installed open-vm-tools,
and has not rebooted yet, they will lose network connection on upgrade
to 237-3ubuntu10.55.
We need
** Changed in: systemd (Ubuntu Bionic)
Status: Fix Released => Fix Committed
--
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/1988119
Title:
systemd-udevd: Run
I just created a new worker nodepool this morning, en redschedulded all
pods to the new workers. Solved it for us.
--
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/1988119
I confirm that Mark Gerrits' approach worked also for my AKS instance.
Tahnk you very much.
--
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/1988119
Title:
systemd-udevd:
** Changed in: systemd (Ubuntu Bionic)
Status: In Progress => 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/1988119
Title:
systemd-udevd: Run
Can confirm we get rid off this issue on our Azure AKS setup; by updating our
NodePool's OS Image to
AKSUbuntu-1804gen2containerd-2022.08.10 (using k8s version 1.22.11)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
@mruffell, spinning up a clean Azure 18.04 Bionic VM and following your
steps + reproducer, I can confirm DNS and network connectivity work
fine:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.6 LTS
Release:18.04
Codename: bionic
I confirm that Sebastiens approach worked also for my AKS instance.
Thank you and to everyone involved, I owe you a pint :)
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1988119/comments/19
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Hi Matthew,
on our production Ubuntu VM in Azure we have problem to ping google.com
The version of prod Ubuntu is:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.5 LTS"
NAME="Ubuntu"
VERSION="18.04.5 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
Hello everyone,
I know there are quite a few people watching this bug, so I will provide
a status update.
The test package has been looking good throughout our internal testing,
and we have proceeded to build the next systemd update, version
237-3ubuntu10.55, and it is currently in the
Sebastien Tardif (sebastientardifverituity) the fix you mentioned works
for me, 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/1988119
Title:
systemd-udevd: Run
@mruffel thank you for the debdiff! With my limited systemd codebase
knowledge, this change feels fine. But I agree with the regression
potential section of the SRU description - we should make sure that the
update is well tested before going out as potentially it can change
behavior.
--
You
@sebastientardifverituity the Microsoft support fix you mentioned worked
for me.
--
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/1988119
Title:
systemd-udevd: Run
Is there an workaround for Azure Container Apps at this point?
--
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/1988119
Title:
systemd-udevd: Run net_setup_link on 'change'
19 matches
Mail list logo
