Bug 1375414

Summary:	atomic-openshift-node not configured with proxy configurations
Product:	OpenShift Container Platform	Reporter:	Peter Larsen <plarsen>
Component:	Installer	Assignee:	Jason DeTiberus <jdetiber>
Status:	CLOSED DUPLICATE	QA Contact:	Johnny Liu <jialiu>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	3.2.1	CC:	aos-bugs, 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:	2016-09-13 13:59:05 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:

Description Peter Larsen 2016-09-13 03:49:16 UTC

Description of problem:
When running the ansible installer directly using openshift_http_proxy and openshift_https_proxy variables in the inventory file, does not modify /etc/sysconfig/atomic-openshift-node with proxy information.

Version-Release number of selected component (if applicable):
oc v3.2.1.15 and v3.2.1.13 both have this problem

How reproducible:
Run the config.yaml playbook with a proxy configuration. The resulting nodes do not have proxy configuration in the /etc/systeconfig/atomic-openshift-node file.

Expected results:
All files, including atomic-openshift-node should be configured with the proper proxy setup.


Additional info:

Comment 1 Scott Dodson 2016-09-13 13:59:05 UTC


*** This bug has been marked as a duplicate of bug 1375031 ***