Bug 1869634

Created attachment 1711713 [details]
cluster is ready while missing dns

Created attachment 1711713 [details]
cluster is ready while missing dns

Description of problem:
Cluster has Ready status although DNS domain is not set. 


Steps to Reproduce:
1.Boot masters and workers with the discovery image. 
2.After nodes registered, assign them role.   
3.Provide the cluster's CIDR and all remaining input except Base DNS Domain.
2. Save changes, and move back to clusters page.

Actual results:
Cluster has Ready status

Expected results:
Cluster has Insufficient status

Additional info:
API returns cluster details w/o the dns validation as expected.

Returned validations_info: "{"hosts-data":[{"id":"all-hosts-are-ready-to-install","status":"success","message":"All hosts in the cluster are ready to install"},{"id":"has-exactly-three-masters","status":"success","message":"Cluster has 3 known master hosts"}],"network":[{"id":"machine-cidr-defined","status":"success","message":"Machine network CIDR is defined"},{"id":"machine-cidr-equals-to-calculated-cidr","status":"success","message":"Cluster machine CIDR equals to the calculated CIDR "},{"id":"api-vip-defined","status":"success","message":"API vip is defined"},{"id":"api-vip-valid","status":"success","message":"api vip 192.168.123.5 belongs to machine CIDR and not in use "},{"id":"ingress-vip-defined","status":"success","message":"Ingress vip is defined"},{"id":"ingress-vip-valid","status":"success","message":"ingress vip 192.168.123.10 belongs to machine CIDR and not in use "}]}"