Hi Coiby,
On Tue, 21 Jun 2022 14:57:17 +0800
Coiby Xu <coxu(a)redhat.com> wrote:
During boot, it may take some time for a device driver to detect the
its devices. By default, NetworkManager doesn't wait for the device to
be available (this is not an issue for the 1st kernel because NM keeps
running in the 1st kernel). So we need to set
connection.wait-device-timeout=60000 [1] as the same to nm-initrd-generator
where does [1] point to?
to tell NM to wait for 6s. Otherwise dracut-kdump-capture.service
would
s/6s/60s/ or fix the comment below.
Thanks
Philipp
fail because network isn't ready. Note the user's custom
value for
wait-device-timeout is respected.
Signed-off-by: Coiby Xu <coxu(a)redhat.com>
---
dracut-module-setup.sh | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/dracut-module-setup.sh b/dracut-module-setup.sh
index dba023d..0105048 100755
--- a/dracut-module-setup.sh
+++ b/dracut-module-setup.sh
@@ -406,6 +406,11 @@ kdump_copy_nmconnection_file() {
_nmconnection_name=$(basename "$_nmconnection_file_path")
_initrd_nmconnection_file_path="/etc/NetworkManager/system-connections/$_nmconnection_name"
inst "$_nmconnection_file_path"
"$_initrd_nmconnection_file_path"
+
+ # Ask NM to wait 60s for the network device to be available
+ # wait-device-timeout=60000 is inserted after "[connection]" so the
+ # user's custom value could overwrite it
+ sed -i '/\[connection\]/a wait-device-timeout=60000'
"${initdir}/$_initrd_nmconnection_file_path"
}
kdump_setup_bridge() {