Bug 1471691

Summary: Can't handle openshift cluster dns in builder containner when do sti build
Product: OpenShift Container Platform Reporter: XiuJuan Wang <xiuwang>
Component: ContainersAssignee: Mrunal Patel <mpatel>
Status: CLOSED CURRENTRELEASE QA Contact: weiwei jiang <wjiang>
Severity: low Docs Contact:
Priority: medium    
Version: 3.6.0CC: amurdaca, aos-bugs, jokerman, lxia, mmccomas, xiuwang
Target Milestone: ---Keywords: Regression
Target Release: 3.6.zFlags: xiuwang: needinfo-
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-11-21 18:38:43 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 XiuJuan Wang 2017-07-17 09:21:44 UTC 
Description of problem:
Could get return when curl app's ip:port, but failed to curl with app's route

Version-Release number of selected component (if applicable):
openshift v3.6.151
kubernetes v1.6.1+5115d708d7

How reproducible:
always

Steps to Reproduce:
1.Prepare an app with route
2.Create app which check step1's route in builder container in same project
$oc new-app ruby https://github.com/openshift-qe/sti-ruby-test.git
$oc patch buildconfig sti-ruby-test -p '{"spec": {"strategy":{"sourceStrategy":{"env":[{"name":"APP_ROUTE","value":"rails-postgresql-example-xiu.0717-n1v.qe.rhcloud.com"}]}}}}'

Actual results:
Build failed to curl route in builder container.

---> Cleaning up unused ruby gems ...
== Assemble ===
54.165.58.205   STREAM rails-postgresql-example-xiu.0717-n1v.qe.rhcloud.com
54.165.58.205   DGRAM
54.165.58.205   RAW
54.82.188.5     STREAM
54.82.188.5     DGRAM
54.82.188.5     RAW


error: build error: non-zero (13) exit code from registry.access.redhat.com/rhscl/ruby-23-rhel7@sha256:ef3ddd245a1d596e2c8ea320d705479a4c293d5a42c058ac82df4da91d8918d8

Expected results:
Could access route in builder contianer
Additional info:
1. Could access step1's route out of  builder container.
2. Could access step1's app ip:port in builder container
3. Here is my change to include app's route in assemble script https://github.com/openshift-qe/sti-ruby-test/blob/master/.sti/bin/assemble#L66
Comment 1 Ben Parees 2017-07-17 14:19:48 UTC 
This is a known issue, the workaround is to include the cluster DNS in the node's /etc/resolv.conf

See further discussion here:
https://trello.com/c/3Mb8EIh0

and here:
https://github.com/openshift/origin/issues/14196

We'll leave this open to track the issue as well.
Comment 2 Ben Parees 2017-09-18 22:22:27 UTC 
According to Mrunal, /etc/resolv.conf is supposed to be getting setup along with the container's networking group, so transferring to him to investigate.
Comment 3 Antonio Murdaca 2018-03-09 17:04:27 UTC 
still an issue guys?
Comment 4 XiuJuan Wang 2018-03-12 08:03:22 UTC 
Can't reproduce this issue in ocp 3.6（latest one is 3.6.173.0.104）and latest OCP 3.9 (v3.9.3) now
Comment 5 XiuJuan Wang 2018-03-12 08:08:00 UTC 
Could you help to set this bug to on_qa? Thanks
Comment 6 XiuJuan Wang 2018-03-13 01:32:23 UTC 
Move this bug to verified as the comment #4