From 8d451dae2767e2d303b3f4cde31ef96c0b0e7c59 Mon Sep 17 00:00:00 2001 From: Gabriel Nagy Date: Wed, 24 Apr 2024 17:25:26 +0300 Subject: [PATCH] Disable systemd-networkd-wait-online on Noble We already did this for Jammy and it appears that Noble exhibits the same issue which causes provisioning to take 2 minutes longer than usual (due to the timing out). What's surprising to me is that we didn't need to do the same for Lunar or Mantic and I'm afraid I don't have a logical explanation for this, but hey... it works! --- e2e/scripts/provision.sh | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/e2e/scripts/provision.sh b/e2e/scripts/provision.sh index ce5512811..39b7a9079 100644 --- a/e2e/scripts/provision.sh +++ b/e2e/scripts/provision.sh @@ -29,11 +29,11 @@ echo "Updating DNS resolver to use AD DNS..." echo "DNS=10.1.0.4" >> /etc/systemd/resolved.conf systemctl restart systemd-resolved -# Work around an issue on Jammy where systemd-networkd times out due to eth0 -# losing connectivity shortly after boot, even though network works fine as -# reported by Azure. -if [ "$(lsb_release -cs)" = "jammy" ]; then - echo "Disabling systemd-networkd-wait-online.service on jammy..." +# Work around an issue on Jammy and Noble where systemd-networkd times out due +# to eth0 losing connectivity shortly after boot, even though network works fine +# as reported by Azure. +if [[ "$(lsb_release -cs)" =~ ^(jammy|noble)$ ]]; then + echo "Disabling misbehaving systemd-networkd-wait-online.service..." systemctl mask systemd-networkd-wait-online.service fi