Description of problem: Survey completed and failed due to not enough hosts found: platform.baremetal.Hosts: Required value: not enough hosts found (5) to support all the configured ControlPlane and Compute replicas (6)] Version-Release number of the following components: 4.6.0-0.nightly-2020-08-27-005538 How reproducible: Always Steps to Reproduce: 1. Provision a dicsonnected env 2. Retrieve the openshift-baremetal-install 3. Run ./openshift-baremetal-install create install-config 4. Fill out all of the questions for 3 masters and 2 workers Actual results: Survey failed to create install-config. Expected results: Install-config created based on survey input. Additional info:
The reason this exits is because the default replicas for workers is the same as the control plane nodes. which is 3. When using the survey (any platform), you must specify 3 worker nodes in addition to 3 masters. I don't think this is a bug.
IMHO, There shouldn't be a minimum number of workers, the survey should also allow a masters only installation. But if the minimum is required, I think it should be noted in the survey when adding hosts and maybe even a verification of matching number of workers.
(In reply to Ori Michaeli from comment #2) > IMHO, > > There shouldn't be a minimum number of workers, the survey should also allow > a masters only installation. > > But if the minimum is required, I think it should be noted in the survey > when adding hosts and maybe even a verification of matching number of > workers. The survey, according to the installer team, is supposed to be minimal and to be generated only with defaults as much as possible, which is what we have done. Their rationale is to create a bare-bones install-config with the suevey and then manually edit it at a later time to make it coherent. From what I can see, the survey is not documented anywhere but if it was documented, we would show this caveat. The validation is working correctly in our platform. Its looking at the replicas (default 3 for masters and workers) and checking at the input. I'll look into moving the validation to a later phase (before cluster creation), which will give an option for the survey to create a default's based insall config.yaml. So, in short, running the following should work with the survey: openshift create install-config But running the following should error until the install-config is coherent (manually edited and corrected): openshift create cluster
I want to reiterate that this is not actually a bug. If the OpenShift Installer survey is documented somewhere it would essentially say that: 1. The survey only produces minimal install-config.yaml file, which is then customized by the end user 2. The survey only accepts defaults for the following values: a. machine network IPs must be in the 10.0.0.0/16 network b. replicas for control plane and workers must be 3 By the way, these defaults/constraints are universal for all platforms and short of redesign of the survey, they cannot be changed. So, I think, if these are documented, then the survey users will know its limitation.
If in case the documentation for the survey doesn't exist or there are no plans for it, then please close this bug.
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira. https://issues.redhat.com/browse/OCPBUGS-8794