Description of problem: Perform an HA installation using atomic-openshift-installer with a preconfigured haproxy server, the proxy host wouldn't have ip and public_ip facts in installer.cfg.yml, which would lead to an error when rerun installer unattended. In ~/.config/openshift/installer.cfg.yml: ... - connect_to: openshift-143.xxx.xxx.com hostname: openshift-143.xxx.xxx.com master_lb: true preconfigured: true public_hostname: openshift-143.xxx.xxx.com Version-Release number of selected component (if applicable): atomic-openshift-utils-3.0.16-1.git.61.2054960.el7aos.noarch How reproducible: Always Steps to Reproduce: 1.[root@openshift-v3 ~]# atomic-openshift-installer install (Input 3 masters, 2 nodes, 1 lb which is pre-configured) *** Installation Summary *** Hosts: - 192.168.0.100 - OpenShift Master - OpenShift Node (Unscheduled) - Etcd Member - 192.168.0.101 - OpenShift Master - OpenShift Node (Unscheduled) - Etcd Member - 192.168.0.102 - OpenShift Node (Dedicated) - 192.168.0.103 - OpenShift Node (Dedicated) - 192.168.0.104 - OpenShift Master - OpenShift Node (Unscheduled) - Etcd Member - openshift-143.xxx.xxx.com - Load Balancer (Preconfigured) ... Do the above facts look correct? [y/N]: N Edit /root/.config/openshift/installer.cfg.yml with the desired values and run `atomic-openshift-installer --unattended install` to restart the install. 2.[root@openshift-v3 ~]# atomic-openshift-installer --unattended install Actual results: [root@openshift-v3 ~]# atomic-openshift-installer --unattended install For unattended installs, facts must be provided for all masters/nodes: Host "openshift-143.xxx.xxx.com" missing facts: ip, public_ip Expected results: Installer shouldn't check the preconfigured lb or the preconfigured lb should also have ip and public_ip facts written in installer.cfg.yml Additional info:
Verify this bug with atomic-openshift-utils-3.0.18-1.git.0.a3e601b.el7aos.noarch. When rerun installer against a preconfigured haproxy server, it wouldn't break again.
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, 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-2015:2667