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

Bug 1767238

Summary: Kibana does not properly inherit all no proxy parameters
Product: OpenShift Container Platform Reporter: Benjamin Milne <bmilne>
Component: InstallerAssignee: ewolinet
Installer sub component: openshift-ansible QA Contact: Johnny Liu <jialiu>
Status: CLOSED DUPLICATE Docs Contact:
Severity: medium    
Priority: unspecified    
Version: 3.11.0   
Target Milestone: ---   
Target Release: 3.11.z   
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: 2019-10-31 22:38:34 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 Benjamin Milne 2019-10-31 00:19:23 UTC
Description of problem:

This is where we see the openshift_no_proxy value being referenced directly. This is pulling straight from Ansible hosts file verbatim:
https://github.com/openshift/openshift-ansible/blob/release-3.11/roles/openshift_logging_kibana/templates/kibana.j2#L162-L169

Here is where the NO_PROXY in /etc/sysconfig/atomic-openshift-node is being populated. I reference this because it is *correct* in the customer's environment. By correct, I mean it has all the stuff from openshift_no_proxy but *more* stuff that is calculated at install time (like the kubernetes.default.svc IP and other junk). You will note that openshift.common.no_proxy is used, that is dynamically calculated during fact gathering.
https://github.com/openshift/openshift-ansible/blob/release-3.11/roles/openshift_node/tasks/configure-proxy-settings.yml#L8-L21

Comment 1 Benjamin Milne 2019-10-31 00:29:25 UTC
Potential Fix for this bug:

https://github.com/openshift/openshift-ansible/pull/11992

Comment 2 Scott Dodson 2019-10-31 22:38:34 UTC

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