Bug 1450310 – Should set NO_PROXY for atomic while using docker system container

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1450310 - Should set NO_PROXY for atomic while using docker system container

Summary:	Should set NO_PROXY for atomic while using docker system container

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Installer (Show other bugs)
Sub Component:
Version:	3.6.0
Hardware:	Unspecified Unspecified

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Steve Milner
QA Contact:	Gan Huang
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1450307
Blocks:
	Show dependency tree / graph

Reported:	2017-05-12 04:51 EDT by Gan Huang
Modified:	2017-08-16 15 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-08-10 01:23:08 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHEA-2017:1716	normal	SHIPPED_LIVE	Red Hat OpenShift Container Platform 3.6 RPM Release Advisory	2017-08-10 05:02:50 EDT

Groups: None (edit)

Description Gan Huang 2017-05-12 04:51:17 EDT

Description of problem:
Currently we only set http_proxy and https_proxy for atomic, this is insufficient for the case that the user needs to set NO_PROXY in /etc/atomic.conf to pull the system container images from the internal registry which doesn't need the proxy.

Version-Release number of selected component (if applicable):
openshift-ansible master branch (last commit id is 593ef65)

How reproducible:
always

Steps to Reproduce:
1. see above
2.
3.

Actual results:
NO_RPOXY not allowed to set in /etc/atomic.conf

Expected results:
Installer should set NO_PROXY in /etc/atomic.conf

Additional info:

Comment 1 Steve Milner 2017-05-12 10:56:24 EDT

NO_PROXY is not supported in /etc/atomic.conf. I've opened up https://github.com/projectatomic/atomic/pull/999 to add it.

Comment 2 Steve Milner 2017-05-12 12:24:02 EDT

PR: https://github.com/openshift/openshift-ansible/pull/4173 (for when atomic:999 is merged)

Comment 3 Steve Milner 2017-05-14 10:32:42 EDT

The PR adds no_proxy to /etc/atomic.conf. However, I don't believe it will be in the current releases so I've added an environment override for the atomic command until atomic:999 is released.

Comment 4 Steve Milner 2017-05-17 10:40:09 EDT

Updated and merged https://github.com/openshift/openshift-ansible/pull/4173

Comment 6 Gan Huang 2017-06-12 03:15:29 EDT

Verified with openshift-ansible-3.6.98-1.git.0.e651d65.el7.noarch.rpm

# grep -nir "no_proxy" /etc/atomic.conf 
26:no_proxy: .cluster.local,openshift-133.xx.redhat.com,openshift-145.xx.redhat.com

Comment 8 errata-xmlrpc 2017-08-10 01:23:08 EDT

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

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