| Summary: | OCP 3.3 ansible installer doesn't support proxy setting for OpenShift Node | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Scott Dodson <sdodson> |
| Component: | Installer | Assignee: | Scott Dodson <sdodson> |
| Status: | CLOSED ERRATA | QA Contact: | Gan Huang <ghuang> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.3.0 | CC: | abutcher, aos-bugs, erich, erjones, ghuang, gkeegan, jialiu, jokerman, knakayam, mmccomas, plarsen, stwalter |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1375031 | Environment: | |
| Last Closed: | 2016-10-03 14:52:45 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: | |
| Bug Depends On: | 1375031 | ||
| Bug Blocks: | |||
|
Comment 1
Scott Dodson
2016-09-13 20:34:49 UTC
Need the cluster network and pod network into NO_PROXY. Please see: https://bugzilla.redhat.com/show_bug.cgi?id=1375031#c18 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. Verified with openshift-ansible-3.3.25-1.git.0.56ee824.el7.noarch 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 |