[4.19-9.6, 4.20-9.6]: s390x: `rhcos.network.init-interfaces-test` timing out

[marmijo]

This test recently started running in the build-node-image job, see: coreos/fedora-coreos-pipeline#1178, and has been failing since on the s390x arch for the 4.19-9.6 and 4.20-9.6 streams.

--- FAIL: rhcos.network.init-interfaces-test (611.87s)
         harness.go:1872: mach.Start() failed: machine "0756884f-e506-4bc6-b471-43b1c7ab7d3f" failed to start: ssh journalctl failed: time limit exceeded

Console Log Analysis

I've reviewed the console logs and believe the machine is actually booting successfully. The log for a test run shows the machine reaching a login prompt and configuring network interfaces.

• Successful boot: The log ends with a console login prompt, although for the ibm-p8-kvm-03-guest-18 user, not the core user.
• Network configuration: The rhcos.network.init-interfaces-test test configures the network via Ignition. The log shows that systemd successfully started the Network Manager service. The final log output also shows three network interfaces (enc1.0001, enc1.0002, and enc3) with assigned IP addresses, confirming the network was successfully configured and is operational.
• coreos-teardown-initramfs: There are some messages from this service: RTNETLINK answers: Operation not supported that I'm not sure are related. The console log shows that the system proceeds to successfully boot despite these messages.

Console.txt from 2025-08-06:

• console.txt

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[travier]

/assign @nikita-dubrovskii

[travier]

/remove-lifecycle stale

[aaradhak]

@nikita-dubrovskii expected to begin work on this in Jan 2026.