Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1583833 - Service load balancers don't work on GCP (and others) that depend on health port being exposed
Service load balancers don't work on GCP (and others) that depend on health p...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer (Show other bugs)
3.10.0
Unspecified Unspecified
high Severity high
: ---
: 3.10.0
Assigned To: Vadim Rutkovsky
Johnny Liu
:
Depends On:
Blocks: 1594306
  Show dependency treegraph
 
Reported: 2018-05-29 16:30 EDT by Clayton Coleman
Modified: 2018-07-30 15:17 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1594306 (view as bug list)
Environment:
Last Closed: 2018-07-30 15:16:51 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1816 None None None 2018-07-30 15:17 EDT

  None (edit)
Description Clayton Coleman 2018-05-29 16:30:06 EDT
The service load balancer on GCP and other clouds creates a health check to the kube-proxy health port on port 10256, and so the port needs to be exposed by the node firewall in order to set up a service load balancer.

Without this service load balancers don't work at all.

https://github.com/openshift/openshift-ansible/pull/8561
Comment 3 Johnny Liu 2018-06-05 21:27:48 EDT
Verified this bug with openshift-ansible-3.10.0-0.60.0.git.0.bf95bf8.el7.noarch, and PASS.

[root@qe-smoke310-master-etcd-1 ~]# iptables -L -n|grep 10256
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp dpt:10256
Comment 6 errata-xmlrpc 2018-07-30 15:16:51 EDT
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:1816

Note You need to log in before you can comment on or make changes to this bug.