Bug 1384750 - Support no_proxy setting for git cloning in OCP
Summary: Support no_proxy setting for git cloning in OCP
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Build
Version: 3.3.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Ben Parees
QA Contact: Wang Haoran
URL:
Whiteboard:
Depends On:
Blocks: 1384753
TreeView+ depends on / blocked
 
Reported: 2016-10-14 04:40 UTC by Kenjiro Nakayama
Modified: 2019-12-16 07:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: Allow a NO_PROXY value to be set for git clone operations in builds Reason: Previously admins could set HTTP_PROXY and HTTPS_PROXY values that would be used for all builds. Certain builds needed to access domains that cannot be reached when going through those default proxies. Adding a NO_PROXY field allows the admin to set domains for which the default proxy value will not be used. Result: Default proxies can be bypassed when performing git clone operations against specific domains.
Clone Of:
Environment:
Last Closed: 2017-01-18 12:42:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Origin (Github) 10902 0 None None None 2016-10-14 04:42:19 UTC
Red Hat Product Errata RHBA-2017:0066 0 normal SHIPPED_LIVE Red Hat OpenShift Container Platform 3.4 RPM Release Advisory 2017-01-18 17:23:26 UTC

Description Kenjiro Nakayama 2016-10-14 04:40:28 UTC 
Description of problem:
===

  There are no way to set no proxy setting for git cloning in S2I build.

Version-Release number of selected component (if applicable):
===

  OCP 3.3

Additional info:
===
  
  Upstream has already implemented this feature as https://github.com/openshift/origin/pull/10902
  I opened this ticket to track for OCP.
Comment 1 Ben Parees 2016-10-14 13:55:53 UTC 
we don't have plans to backport this to 3.3.1 and it's been merged for 3.4.0, so what would you like us to do w/ this bug?
Comment 3 Troy Dawson 2016-10-18 15:56:07 UTC 
This has been merged into ose and is in OSE v3.4.0.12 or newer.
Comment 5 wewang 2016-10-19 06:56:33 UTC 
I think cases:535467,535465 can cover the bug ,and tested cases in version:
openshift v3.4.0.12
kubernetes v1.4.0+776c994
etcd 3.1.0-alpha.1

it works as expected results of cases.
Comment 7 errata-xmlrpc 2017-01-18 12:42:49 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-2017:0066
Note You need to log in before you can comment on or make changes to this bug.