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

Bug 1589692

Summary: "oc logs/rsh" command failed when cluster is running behind proxy
Product: OpenShift Container Platform Reporter: Johnny Liu <jialiu>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED DEFERRED QA Contact: Johnny Liu <jialiu>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.9.0CC: aos-bugs, jokerman, mmccomas, wmeng
Target Milestone: ---   
Target Release: 3.9.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: 2018-11-19 18:27:28 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:
Attachments:
Description Flags
installation log with inventory file embedded none

Description Johnny Liu 2018-06-11 08:20:05 UTC 
Created attachment 1449933 [details]
installation log with inventory file embedded

Description of problem:

Version-Release number of the following components:
openshift-ansible-3.9.30-1.git.7.46f8678.el7.noarch

How reproducible:
Always

Steps to Reproduce:
1. Running an installation behind proxy
2. after installation, on master, run "oc logs/rsh" command
3.

Actual results:
[root@qe-jialiu393-master-etcd-nfs-1 ~]# oc logs docker-registry-1-hs75z
Error from server: Get https://qe-jialiu393-node-registry-router-1:10250/containerLogs/default/docker-registry-1-hs75z/registry: dial tcp: lookup qe-jialiu393-node-registry-router-1 on 10.11.5.19:53: no such host

[root@qe-jialiu393-master-etcd-nfs-1 ~]# oc rsh docker-registry-1-hs75z
Error from server: error dialing backend: dial tcp: lookup qe-jialiu393-node-registry-router-1 on 10.11.5.19:53: no such host

[root@qe-jialiu393-master-etcd-nfs-1 ~]# ping qe-jialiu393-node-registry-router-1
PING qe-jialiu393-node-registry-router-1.openshift-snvl2.internal (192.168.100.7) 56(84) bytes of data.
64 bytes from 192.168.100.7 (192.168.100.7): icmp_seq=1 ttl=64 time=0.455 ms

Expected results:
"oc logs/rsh" command passed.

Additional info:
"qe-jialiu393-node-registry-router-1" is already added into NO_PROXY list in master config file.
[root@qe-jialiu393-master-etcd-nfs-1 ~]# grep "NO_PROXY" /etc/sysconfig/atomic-openshift-master-api
NO_PROXY=.centralci.eng.rdu2.redhat.com,.cluster.local,.svc,169.254.169.254,172.30.0.1,192.168.100.9,qe-jialiu393-master-etcd-nfs-1,qe-jialiu393-node-registry-router-1,172.30.0.0/16,10.128.0.0/14
[root@qe-jialiu393-master-etcd-nfs-1 ~]# grep "NO_PROXY" /etc/sysconfig/atomic-openshift-master-controllers 
NO_PROXY=.centralci.eng.rdu2.redhat.com,.cluster.local,.svc,169.254.169.254,172.30.0.1,192.168.100.9,qe-jialiu393-master-etcd-nfs-1,qe-jialiu393-node-registry-router-1,172.30.0.0/16,10.128.0.0/14

After restart master api/controller service, "oc rsh/logs" works well.
Comment 1 Russell Teague 2018-11-19 18:27:28 UTC 
There appear to be no active cases related to this bug. As such we're closing this bug in order to focus on bugs that are still tied to active customer cases. Please re-open this bug if you feel it was closed in error or a new active case is attached.