kdump fix, initializing network interface on crash kernel boot over master release #18833
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
For pre-boot initialization of network interfaces.
For my case, I had to test and implement the remote kdump file transfer using SSH and the crash kernel did not load configs from /etc/network/interfaces config file.
How I did it
New file created for a custom script, "network-interface-state-init.sh"
Modified the "build_debian.sh" file for adding this to the /usr/sbin/network-interface-state-init.sh.
How to verify it
After this change the remote SSH kdump file transfer would be possible because network not reachable issue arose as the default crash kernel image did not change state of the interfaces to "UP" upon load. Neither did it load configs from /etc/network/interfaces config file.