Hi, I am a little eager to add this without trying to resort to other solutions first.
So, options are:
1) For some reason, this driver is not behaving correctly. Can you add the PowerIO folks to this bug on IBM side and let them do some investigation?
2) network-online is not doing the correct thing. Well, from what I read, they indeed don't care much about this and think the program should wait for the network to be available. After eliminating 1, we should look into why network-online decides the network is online or why systemd would start kdump after that, and the ssh host would still not be reachable.
3) I would rather add the timeout but also conditionally checking for the host availability. That is: wait until it's available, then dump. If not available for the timeout duration, reboot.
Hi, I am a little eager to add this without trying to resort to other solutions first.
So, options are:
1) For some reason, this driver is not behaving correctly. Can you add the PowerIO folks to this bug on IBM side and let them do some investigation?
2) network-online is not doing the correct thing. Well, from what I read, they indeed don't care much about this and think the program should wait for the network to be available. After eliminating 1, we should look into why network-online decides the network is online or why systemd would start kdump after that, and the ssh host would still not be reachable.
3) I would rather add the timeout but also conditionally checking for the host availability. That is: wait until it's available, then dump. If not available for the timeout duration, reboot.