Bug 1298787
Summary: | [RFE]openshift-ansible should support containerized ha-master installation | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ma xiaoqiang <xiama> |
Component: | Installer | Assignee: | Scott Dodson <sdodson> |
Status: | CLOSED ERRATA | QA Contact: | Gan Huang <ghuang> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 3.1.0 | CC: | aos-bugs, bleanhar, jialiu, jokerman, jonstanley, mmccomas, stwalter, xtian |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-04-12 18:47:06 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ma xiaoqiang
2016-01-15 04:04:11 UTC
Install ha-master env. QE met the following error: TASK: [haproxy | Configure haproxy] ******************************************* <--snip--> msg: Destination directory /etc/haproxy does not exist FATAL: all hosts have already failed -- aborting This is being tracked here: https://trello.com/c/ggjBrhgO/169-support-containerized-haproxy-for-ha-environments-using-lb-hosts Community contribution which deploys the load balancer using the existing haproxy image https://github.com/openshift/openshift-ansible/pull/3106 openshift-ansible-3.5.3-1 and newer should allow for containerized=true for lb hosts it makes use of the existing router image for haproxy. Verified with openshift-ansible-3.5.45-1.git.0.eb0859b.el7.noarch Step: 1) Trigger installation with containerized Haproxy host #cat inventory_hosts <--snip--> openshift_master_console_port=443 openshift_master_api_port=443 [lb] openshift-xxx.com containerized=true Result: 1) Installation successfully 2) Docker was installed and Haproxy container run well on Haproxy host 3) Succeed to login Web console via haproxy hostname 4) S2I build succeed 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-2017:0903 |