Bug 2064708

.The `kdump` service fails to build the `initrd` file on IBM Z systems On the 64-bit IBM Z systems, the `kdump` service fails to load the initial RAM disk (`initrd`) when `znet` related configuration information such as `s390-subchannels` reside in an inactive `NetworkManager` connection profile. Consequently, the `kdump` mechanism fails with the following error: ---- dracut: Failed to set up znet kdump: mkdumprd: failed to make kdump initrd ---- As a workaround, use one of the following solutions: * Configure a network bond or bridge by re-using the connection profile that has the `znet` configuration information: + ---- $ nmcli connection modify enc600 master bond0 slave-type bond ---- * Copy the `znet` configuration information from the inactive connection profile to the active connection profile: .. Run the `nmcli` command to query the `NetworkManager` connection profiles: + ---- # nmcli connection show NAME UUID TYPE Device bridge-br0 ed391a43-bdea-4170-b8a2 bridge br0 bridge-slave-enc600 caf7f770-1e55-4126-a2f4 ethernet enc600 enc600 bc293b8d-ef1e-45f6-bad1 ethernet -- ---- .. Update the active profile with configuration information from the inactive connection: + ---- #!/bin/bash inactive_connection=enc600 active_connection=bridge-slave-enc600 for name in nettype subchannels options; do field=802-3-ethernet.s390-$name val=$(nmcli --get-values "$field"connection show "$inactive_connection") nmcli connection modify "$active_connection" "$field" $val" done ---- .. Restart the `kdump` service for changes to take effect: + ---- # kdumpctl restart ----