Bug 1594306 - Service load balancers don't work on GCP (and others) that depend on health port being exposed
Summary: Service load balancers don't work on GCP (and others) that depend on health p...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.9.z
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1583833
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-22 15:10 UTC by Eduardo Minguez
Modified: 2018-07-18 09:19 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Port 10256 is now opened on hosts which resolves an issue where service load balancer health checks failed because the port was not opened.
Clone Of: 1583833
Environment:
Last Closed: 2018-07-18 09:18:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2213 0 None None None 2018-07-18 09:19:11 UTC

Comment 1 Scott Dodson 2018-06-22 17:09:11 UTC 
https://github.com/openshift/openshift-ansible/pull/8928
Comment 3 Johnny Liu 2018-06-28 07:10:47 UTC 
No testable rpm installer yet.
Comment 4 Johnny Liu 2018-07-10 06:07:33 UTC 
Verified this bug with openshift-ansible-3.9.33-1.git.56.19ba16e.el7.noarch, and PASS.

[root@qe-smoke39-mrrn-1 ~]# iptables -L -n|grep 10256
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp dpt:10256
[root@qe-smoke39-mrrn-1 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 7.5 (Maipo)
[root@qe-smoke39-mrrn-1 ~]# uname -a
Linux qe-smoke39-mrrn-1 3.10.0-862.6.3.el7.x86_64 #1 SMP Fri Jun 15 17:57:37 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
Comment 6 errata-xmlrpc 2018-07-18 09:18:59 UTC 
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-2018:2213
Note You need to log in before you can comment on or make changes to this bug.