Bug 1414748
Summary: | Proxy settings misconfigured | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Marko Myllynen <myllynen> |
Component: | Installer | Assignee: | Tim Bielawa <tbielawa> |
Status: | CLOSED ERRATA | QA Contact: | Gan Huang <ghuang> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 3.4.0 | CC: | aos-bugs, jokerman, mmccomas, myllynen, xtian |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: OpenShift Ansible facts were splitting a configuration parameter incorrectly.
Consequence: Invalid 'NO_PROXY' strings were generated and inserted into user docker sysconfig files.
Fix: Reviewed and fixed the logic that generates the NO_PROXY strings.
Result: Valid docker NO_PROXY settings are generated and inserted into the sysconfig/docker file now.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-10 05:17:28 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
Marko Myllynen
2017-01-19 11:08:57 UTC
Which installer version are you using? Seeing this with latest official 3.3/3.4 packages, e.g., 3.4.44-1.git.0.efa61c6.el7. Thanks. Fixed the merge conflicts and re-running the jenkins tests now. Rerunning the test suites on this now. Maybe they'll pass this time. Testing is running on this again. Verified with openshift-ansible-3.6.135-1.git.0.5533fe3.el7.noarch.rpm #cat inventory_hosts <--snip--> openshift_no_proxy=".cluster.local,.lab.sjc.redhat.com,10.1.0.0/16,172.30.0.0/16" <--snip--> Installation succeed and no_proxy created correctly # grep 'NO_PROXY' /etc/sysconfig/docker NO_PROXY='.cluster.local,.lab.sjc.redhat.com,.svc,10.1.0.0/16,172.30.0.0/16,ip-172-18-9-154.ec2.internal' 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/RHEA-2017:1716 |