Try to bring up the most recently used NetworkManager connection profiles

Resolves: https://issues.redhat.com/browse/KEX-344

Currently, the nfs_ovs plan fails because nm-wait-online-initrd.service
waits for the bonding network to be created. But the bonding network
can't be activated because the eth0 NM connection is brought up first
which stops the slave connnection profile to be activated,

/var/lib/NetworkManager/timestamps keeps the timestamps of NM
connections when they are lastly used. When multiple NM connections have
the same connection.autoconnect-priority, the latest used NM connection
will be activated.

[1] https://networkmanager.dev/docs/api/latest/settings-connection.html

Fixes: 3f4a9eb ("Bring up the network before Open vSwitch bridge")
Signed-off-by: Coiby Xu <[email protected]>

Author: coiby

dracut/99kdumpbase/module-setup.sh

@@ -344,6 +344,7 @@ _install_nmconnections_before_ovs() {
             exit 1
         fi
     done <<< "$(nmcli --get-values filename,ACTIVE connection show | grep "no$")"
+    inst /var/lib/NetworkManager/timestamps
 }
 
 kdump_install_nmconnections() {