Bug 1384750
| Summary: | Support no_proxy setting for git cloning in OCP | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Kenjiro Nakayama <knakayam> |
| Component: | Build | Assignee: | Ben Parees <bparees> |
| Status: | CLOSED ERRATA | QA Contact: | Wang Haoran <haowang> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3.0 | CC: | aos-bugs, knakayam, pep, tdawson, wewang |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-18 12:42:49 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1384753 | ||
|
Description
Kenjiro Nakayama
2016-10-14 04:40:28 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? This has been merged into ose and is in OSE v3.4.0.12 or newer. 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. 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 |