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 "}]}"
May be related: Creating a cluster with API call POST to /clusters only requires cluster name and openshift version to succeed. The pull secret while required in UI is not validated by the back end.
As per Nir comment: According to Liat G., creating a cluster w/o a pull secret is a valid flow. But, there are more validations before installations and cluster should not be Ready in case of missing pull secret. adding more test to cover this pull secret.
Issue validated on latest (deployed at Aug 25).
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.6.13 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:0171