At some customers they have custom networking done by configuring stuff at /etc/nmstate that is applied on nmstate.service, the machine-config-daemon-pull systemd unit need connectivity to pull images so it should depend on applied stuff at /etc/nmstate but ensuring the nmstate.service is call.

This should be fixed by making machine-config-daemon-pull systemd unit depend on nmstate.service unit.

    4.20

    Always

    1. Create a node without default gw
    2. Configure default gw with MC creating a /etc/nmstate/99-gw.yaml to configure it
    3. Install openshift using it 
    

machine-config-daemon-pull fails since it's not able to pull the images    

The nmstate.service should kick in before machine-config-daemon-pull and so the 99-gw.yaml configure the proper default gw and the image can be pull

Discover as part of customer using hypershift kubevirt cluster where defautl gw is not configured with DHCP.