I'm able to enter the same IP Address for both API and Ingress prompts. Of course, this is user error but some validation on this would be helpful in the event of a mistake. Creating a cluster with these settings results in Bootstrap and one of the masters being assigned the same IP address during installation. $ ./openshift-install create cluster ... ? Virtual IP Address for API 10.50.0.10 ? Virtual IP Address for Ingress 10.50.0.10
checked on nightly build 4.5.0-0.nightly-2020-07-02-190154 when launching "./openshift-install create cluster", and input same IP on both apiVIP and ingressVIP, it is indeed no such checking and installation is on-going, since bootstrap server and one master node hold same VIP, installation is failed when waiting for bootstrapping complete Test again with same build, and input correct apiVIP and ingressVIP(two different IPs), and installation is successful.
We should definitely address this. This shouldn't be a GA blocker though.
This is under active code review, but possibly will not merge today so we are adding UpcomingSprint.
PR got merged so removing UpcomingSprint.
Verified on nightly build: 4.6.0-0.nightly-2020-08-03-225825, and passed. # ./openshift-install create cluster --dir ./install ? SSH Public Key /root/.ssh/openshift-qe.pub ? Platform vsphere ? vCenter xxxxxx ? Username xxxxx ? Password [? for help] ************ INFO Connecting to xxxxxxx INFO Defaulting to only available datacenter: dc1 INFO Defaulting to only available cluster: devel ? Default Datastore nvme-ds1 INFO Defaulting to only available network: VM Network ? Virtual IP Address for API 192.168.2.2 X Sorry, your reply was invalid: "192.168.2.2" should not be equal to the Virtual IP address for the API ? Virtual IP Address for Ingress [? for help]
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 (OpenShift Container Platform 4.6 GA Images), 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/RHBA-2020:4196