Bug 1375414 - atomic-openshift-node not configured with proxy configurations
Summary: atomic-openshift-node not configured with proxy configurations
Keywords:
Status: CLOSED DUPLICATE of bug 1375031
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.2.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Jason DeTiberus
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-13 03:49 UTC by Peter Larsen
Modified: 2016-09-13 13:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-13 13:59:05 UTC
Target Upstream Version:

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

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 ***
Note You need to log in before you can comment on or make changes to this bug.