Bug 1375723 - OCP 3.3 ansible installer doesn't support proxy setting for OpenShift Node
Summary: OCP 3.3 ansible installer doesn't support proxy setting for OpenShift Node
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.3.0
Hardware: All
OS: Linux
high
medium
Target Milestone: ---
: ---
Assignee: Scott Dodson
QA Contact: Gan Huang
URL:
Whiteboard:
Depends On: 1375031
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-13 20:33 UTC by Scott Dodson
Modified: 2017-03-08 18:26 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Previously, the installer did not configure proxy settings for the node service. In some cases this is required for the node service to communicate with the cloud provider which would have prevented the node from starting properly. The installer has been updated to configure proxy settings for the node service ensuring the node can communicate with the cloud API when a proxy is required to do so.
Clone Of: 1375031
Environment:
Last Closed: 2016-10-03 14:52:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1983 0 normal SHIPPED_LIVE OpenShift Container Platform 3.3 atomic-openshift-utils bug fix update 2016-10-03 18:51:38 UTC

Comment 1 Scott Dodson 2016-09-13 20:34:49 UTC 
Fixed in https://github.com/openshift/openshift-ansible/pull/2443
Comment 2 Gan Huang 2016-09-18 08:33:50 UTC 
Need the cluster network and pod network into NO_PROXY.
Please see:
https://bugzilla.redhat.com/show_bug.cgi?id=1375031#c18
Comment 4 Gan Huang 2016-09-20 06:11:14 UTC 
Should be the same issue with https://bugzilla.redhat.com/show_bug.cgi?id=1375031#c24

Will test again when the fix is pushed to new errata puddle.
Comment 6 Gan Huang 2016-09-21 04:27:38 UTC 
Verified with openshift-ansible-3.3.25-1.git.0.56ee824.el7.noarch
Comment 8 errata-xmlrpc 2016-10-03 14:52:45 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-2016:1983
Note You need to log in before you can comment on or make changes to this bug.