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

Bug 1596752

Summary: Better to display hostname under EGRESS_DNS_PROXY_DESTINATION when use configMap
Product: OpenShift Container Platform Reporter: Weibin Liang <weliang>
Component: ocAssignee: Juan Vallejo <jvallejo>
Status: CLOSED NOTABUG QA Contact: Xingxing Xia <xxia>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.10.0CC: aos-bugs, bbennett, jokerman, maszulik, mmccomas
Target Milestone: ---   
Target Release: 3.11.0   
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-07-04 13:42:03 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
Include configMap-dns.txt and egress-dns-pod-configmap.yaml none

Description Weibin Liang 2018-06-29 15:40:26 UTC
Created attachment 1455532 [details]
Include configMap-dns.txt and egress-dns-pod-configmap.yaml

Description of problem:
Better to display hostname under EGRESS_DNS_PROXY_DESTINATION when use configMap for egress router dns proxy mode configuration

Version-Release number of selected component (if applicable):
v3.10.0-rc.0+9453255-21


How reproducible:
Every time

Steps to Reproduce:
1.oc create configmap egress-router --from-file=destination=configMap-dns.txt
2.oc create -f egress-dns-pod-configmap.yaml
2.oc describe pod egress-dns-pod


Actual results:
[root@openshift-master /]# oc describe pod egress-dns-pod
Environment:
      EGRESS_DNS_PROXY_DEBUG:        1
      EGRESS_DNS_PROXY_DESTINATION:  <set to the key 'destination' of config map 'egress-router'>  Optional: false


Expected results:
Environment:
      EGRESS_DNS_PROXY_DEBUG:        1
      EGRESS_DNS_PROXY_DESTINATION:  80     www.google.com
                                     8000   209.82.215.211 80
                                     8001   www.yahoo.com  80

Additional info:

Comment 1 Dan Mace 2018-07-03 15:14:51 UTC
I don't think this is a bug. I doubt the intent of the generic pod describer is to print the contents of a configmap key reference, but I'll pass this over to the CLI component for the final word before closing.

Comment 2 Juan Vallejo 2018-07-03 20:13:16 UTC
I agree with Dan, although it would be convenient in this case to display the hostnames referenced by the assigned configMap key, this might not be as useful in cases where you point to a configMap key storing hundreds of lines from a file, for example.

By providing users with the key and configMap name instead, a user can explicitly choose to perform a second `oc describe` command on that configmap, and view its full contents then.

Adding Maciej for his opinion.

Comment 3 Maciej Szulik 2018-07-04 13:42:03 UTC
This is working as expected. The example you're giving here is using only 2 elements, what if the cm will have significantly more. I'm closing this as not a bug.