Bug 1335063 - [Behind Proxy] Master service can't recognize quoted proxy variables in container installation
Summary: [Behind Proxy] Master service can't recognize quoted proxy variables in conta...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Devan Goodwin
QA Contact: Ma xiaoqiang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-11 09:09 UTC by Gan Huang
Modified: 2017-01-22 02:47 UTC (History)
6 users (show)

Fixed In Version: openshift-ansible-3.0.90-1
Doc Type: Bug Fix
Doc Text:
The installer's global proxy configuration incorrectly quoted values in the master's sysconfig files. This meant that containerized installs using proxy configurations created by the installer would have failed. The installer has been updated to use proper quoting syntax.
Clone Of:
Environment:
Last Closed: 2016-06-07 10:56:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1208 0 normal SHIPPED_LIVE Red Hat OpenShift Enterprise atomic-openshift-utils bug fix update 2016-06-07 14:55:01 UTC

Comment 5 Gan Huang 2016-05-16 09:58:12 UTC
Please move to ON_QA once commited to package atomic-openshift-utils.

Comment 6 Devan Goodwin 2016-05-17 15:17:31 UTC
Should be fixed in the latest tagged version Gan. Added fixed in version above.

Comment 8 Gan Huang 2016-05-19 06:44:24 UTC
Verified with openshift-ansible-3.0.90-1.git.0.a077b68.el7.noarch

* Now quotes are removed in master configurations. 
* Imagestream tags can be updated and sti-build successfully in rpm and container installation.

After removing master hostname from NO_PROXY. Master service can't be restarted.
So NO_PROXY is working too.

Move it to verified.

Comment 10 errata-xmlrpc 2016-06-07 10:56:12 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:1208


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