Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1498325

Summary:	no_proxy environment variable should be a standard format
Product:	OpenShift Container Platform	Reporter:	Takayoshi Tanaka <tatanaka>
Component:	ImageStreams	Assignee:	kconner
Status:	CLOSED UPSTREAM	QA Contact:	Dongbo Yan <dyan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6.1	CC:	aos-bugs, bparees, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-25 21:01:01 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 Takayoshi Tanaka 2017-10-04 01:56:21 UTC

Description of problem:
Java s2i image requires "no_proxy" environment variable is a non-standard format like "*.foo.com,*.bar.com". This causes other tools (e.g. curl) not to work properly.
This specification is described here.
https://access.redhat.com/documentation/en-us/red_hat_jboss_middleware_for_openshift/3/html-single/red_hat_java_s2i_for_openshift/#configuration_environment_variables


Version-Release number of selected component (if applicable):
redhat-openjdk-18/openjdk18-openshift:1.1-11 
https://access.redhat.com/containers/?tab=overview#/registry.access.redhat.com/redhat-openjdk-18/openjdk18-openshift
and so on.

How reproducible:
Always

Steps to Reproduce:
1. Create a new app with s2i Java image under proxy server.
2. Set no_proxy like "no_proxy=*.google.com"

Actual results:
Failed to execute curl command.
$ curl http://www.google.com

Expected results:
Curl command executes without errors.

Additional info:

Comment 1 Ben Parees 2017-10-04 02:07:46 UTC

Kevin Conner's team owns this image, but they handle their issues in JIRA so he's likely going to want you to open it there.

Comment 2 Takayoshi Tanaka 2017-10-04 02:09:50 UTC

Could you tell me the JIRA URL?

Comment 3 Takayoshi Tanaka 2017-10-04 06:03:31 UTC

Though I'm not familiar with Java, will the below JIRA ticket fix this issue?
https://issues.jboss.org/browse/CLOUD-2020

Comment 4 Takayoshi Tanaka 2017-10-04 23:54:54 UTC

Since the previous JIRA ticket is not enough to fix this issue according to the customer , I file a new ticket.
https://issues.jboss.org/browse/CLOUD-2084

Comment 5 Ben Parees 2017-10-25 21:01:01 UTC

As this is not an openshift issue and the owning team tracks issues via JIRA, I am closing this bug.

Takayoshi, if you need a BZ to track this for the customer, please work w/ the middleware team to find a more appropriate BZ product/component to assign this to.