Blame 2134-revert-avoid-restarting-NetworkManager.patch

7a74f7
From 5dc6aede4b99f1c76219370660b5b62e935a3cb8 Mon Sep 17 00:00:00 2001
7a74f7
From: Lubomir Rintel <lkundrak@v3.sk>
7a74f7
Date: Tue, 20 Dec 2022 13:06:43 +0100
7a74f7
Subject: [PATCH] revert(network-manager): avoid restarting NetworkManager
7a74f7
7a74f7
This reverts commit 77630365aed201a729c73a9ffda0733a75f3fee4.
7a74f7
7a74f7
Its commit message states:
7a74f7
7a74f7
  On EL8.3 the NetworkManager keep restarting even if it exits successfully
7a74f7
  while waiting for Clevis to unlock. This patch ensures NetworkManager runs
7a74f7
  only once in initrd.
7a74f7
7a74f7
Yes; NetworkManager is run multiple times, so that it's able to
7a74f7
configure interfaces that haven't been seen previously (because bus was
7a74f7
slow to scan or device took time to initialize).
7a74f7
7a74f7
It's not clear what problem was the original commit trying to fix.
7a74f7
I suspect there was no problem, just a misunderstanding.
7a74f7
---
7a74f7
 modules.d/35network-manager/nm-run.sh | 4 ----
7a74f7
 1 file changed, 4 deletions(-)
7a74f7
7a74f7
diff --git a/modules.d/35network-manager/nm-run.sh b/modules.d/35network-manager/nm-run.sh
7a74f7
index 7d8d61fa7..14b9cb1ad 100755
7a74f7
--- a/modules.d/35network-manager/nm-run.sh
7a74f7
+++ b/modules.d/35network-manager/nm-run.sh
7a74f7
@@ -2,10 +2,6 @@
7a74f7
 
7a74f7
 type source_hook > /dev/null 2>&1 || . /lib/dracut-lib.sh
7a74f7
 
7a74f7
-if [ -e /tmp/nm.done ]; then
7a74f7
-    return
7a74f7
-fi
7a74f7
-
7a74f7
 if [ -z "$DRACUT_SYSTEMD" ]; then
7a74f7
     # Only start NM if networking is needed
7a74f7
     if [ -e /run/NetworkManager/initrd/neednet ]; then