We tried to fix DNS propagation in this patch. https://github.com/openshift/ci-tools/pull/3687

Essentially we have an IPI libvirt workflow that should "wrap" all substeps with a DNSConfig unless it is set explicitly. Unfortunately, the step configuration resolution isn't working, as evidenced by the test job we've set up to restore kdump to the RT jobs.

Specifically this PR running on build01:
https://github.com/openshift/release/pull/44057Specifically this job:
https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_rele[…]-4.14-ocp-e2e-ovn-remote-libvirt-s390x/1745825793059065856The expectation is that the IPI libvirt workflow will override its descendants:
https://github.com/openshift/release/blob/4918f524aa8456f96eadf3cbafee1839ddba3093/ci-operator/step-registry/ipi/libvirt/ipi-libvirt-workflow.yamlAdditionally, for this PR, I've added a theoretically unnecessary special override for the dnsConfig to the step in the chain def:
https://github.com/openshift/release/blob/4918f524aa8456f96eadf3cbafee1839ddba3093[…]ator/step-registry/ipi/libvirt/post/ipi-libvirt-post-chain.yamlBut if we look at the test run, we can see that it fails to resolve the target host, which it should be getting from the DNS server specified above
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshi[…]/ipi-conf-debug-kdump-gather-logs/build-log.txt
12:05
The underlying step is defined here: https://github.com/openshift/release/blob/4918f524aa8456f96eadf3cbafee1839ddba3093[…]bug/kdump-gather-logs/ipi-conf-debug-kdump-gather-logs-ref.yaml
Which should only overwrite the dnsConfig IF it were explicitly defined in this step.