I have seen this consistently in dev-scripts when running SNO_IPV4 with 4.13. One particular version I just duplicated it with is registry.ci.openshift.org/ocp/release:4.13.0-0.nightly-2023-03-22-165711
I'm not running with any additional patches, nor am I mirroring images

What occurs is that the installation works fine until reboot, I see from the wait-for:

level=info msg=Bootstrap Kube API Initialized
level=info msg=Host: master-0, reached installation stage Writing image to disk
level=info msg=Host: master-0, reached installation stage Writing image to disk: 13%
level=info msg=Host: master-0, reached installation stage Writing image to disk: 18%
level=info msg=Host: master-0, reached installation stage Writing image to disk: 23%
level=info msg=Host: master-0, reached installation stage Writing image to disk: 36%
level=info msg=Host: master-0, reached installation stage Writing image to disk: 43%
level=info msg=Host: master-0, reached installation stage Writing image to disk: 48%
level=info msg=Host: master-0, reached installation stage Writing image to disk: 56%
level=info msg=Host: master-0, reached installation stage Writing image to disk: 63%
level=info msg=Host: master-0, reached installation stage Writing image to disk: 71%
level=info msg=Host: master-0, reached installation stage Writing image to disk: 78%
level=info msg=Host: master-0, reached installation stage Writing image to disk: 84%
level=info msg=Host: master-0, reached installation stage Writing image to disk: 92%
level=info msg=Host: master-0, reached installation stage Writing image to disk: 100%

After that it hangs until it eventually times out. When I go into the console I see the attached screenshot. Basically it is hanging on:
"A start job is running for Writes IP address configuration so that kubelet and crio services select a valid node IP" The timer next to it just keeps counting up.

I see a related bug has been fixed in assisted-service - 
Bug https://issues.redhat.com//browse/MGMT-13240
Fix https://github.com/openshift/assisted-service/pull/4892

However I was not using DHCP and it looks like that particular fix is in 4.13-release so the version I'm testing has the fix.

4.13.0-0.nightly-2023-03-22-165711

Happens every time

1.
2.
3.