| Summary: | Remove HTTP{s}_PROXY references from /etc/sysconfig/atomic-openshift-* | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | thunt |
| Component: | Installer | Assignee: | Scott Dodson <sdodson> |
| Status: | CLOSED NOTABUG | QA Contact: | Gan Huang <ghuang> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.1.0 | CC: | aos-bugs, jokerman, mmccomas, thunt |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-09-19 19:54:53 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
thunt
2016-02-23 15:00:17 UTC
Makes sense, I can think of no reason the node would need a proxy in the vast majority of configurations. You've confirmed in environments where proxies are required that running the node without these envars works fine? Yes, and and under all normal use cases if the proxy is defined, it breaks the configuration. Th only time we would need a proxy would be if that was the only way to reach the master, and I never expect to see that configuration. https://github.com/openshift/origin/pull/8683 This is also fixed in ansible in https://github.com/openshift/openshift-ansible/pull/1385 Test with openshift-ansible-3.0.90-1.git.0.a077b68.el7.noarch
Config http_proxy and https_proxy in inventory hosts. Check configurations after installation.
[root@xxx ~]# cat /etc/sysconfig/atomic-openshift-node
OPTIONS=--loglevel=5
# /etc/origin/node/ should contain the entire contents of
# /var/lib/origin.local.certificates/node-${node-fqdn} generated by
# running 'atomic-enterprise admin create-node-config' on your master
#
# If if your node is running on a separate host you can rsync the contents
# rsync -a root@atomic-enterprise-master:/var/lib/origin/origin.local.certificates/node-`hostname`/ /etc/origin/node
CONFIG_FILE=/etc/origin/node/node-config.yaml
# The $DOCKER_NETWORK_OPTIONS variable is used by sdn plugins to set
# $DOCKER_NETWORK_OPTIONS variable in the /etc/sysconfig/docker-network
# Most plugins include their own defaults within the scripts
# TODO: More elegant solution like this
# https://github.com/coreos/flannel/blob/master/dist/mk-docker-opts.sh
# DOCKER_NETWORK_OPTIONS='-b=lbr0 --mtu=1450'
# Proxy configuration
# Origin uses standard HTTP_PROXY environment variables. Be sure to set
# NO_PROXY for your master
#NO_PROXY=master.example.com
#HTTP_PROXY=http://USER:PASSWORD@IPADDR:PORT
#HTTPS_PROXY=https://USER:PASSWORD@IPADDR:PORT
IMAGE_VERSION=
Proxy config is removed from /etc/sysconfig/atomic-openshift-node.
But proxy references are still present in /etc/sysconfig/atomic-openshift-node.
Experienced in rpm installation only. It actually turns out that nodes needs proxy config in particular for cloud providers. See https://bugzilla.redhat.com/show_bug.cgi?id=1375031 |