If a customer uses non-standard domain in install-config.yaml openshift-install creates agent.iso without issue but in later stage of installation steps it will not get further. It could make sense to have a domain validation part of agent create image -command so this kind of wrong configuration could be blocked as early as possible.

4.16.36    

    Easily can be produced

    1. define non-standard domain name in install-config.yaml like mydomain.x (in this case one letter root domain is not following standard)
    2. create a new agent.iso
    3. spin up a new openshift deployment and check journal logs