Bug 1471691 - Can't handle openshift cluster dns in builder containner when do sti build
Can't handle openshift cluster dns in builder containner when do sti build
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers (Show other bugs)
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Mrunal Patel
DeShuai Ma
: Regression
Depends On:
  Show dependency treegraph
Reported: 2017-07-17 05:21 EDT by XiuJuan Wang
Modified: 2018-03-12 21:32 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
xiuwang: needinfo-

Attachments (Terms of Use)

  None (edit)
Description XiuJuan Wang 2017-07-17 05:21:44 EDT
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:

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 ===   STREAM rails-postgresql-example-xiu.0717-n1v.qe.rhcloud.com   DGRAM   RAW     STREAM     DGRAM     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 10:19:48 EDT
This is a known issue, the workaround is to include the cluster DNS in the node's /etc/resolv.conf

See further discussion here:

and here:

We'll leave this open to track the issue as well.
Comment 2 Ben Parees 2017-09-18 18:22:27 EDT
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 12:04:27 EST
still an issue guys?
Comment 4 XiuJuan Wang 2018-03-12 04:03:22 EDT
Can't reproduce this issue in ocp 3.6(latest one is latest OCP 3.9 (v3.9.3) now
Comment 5 XiuJuan Wang 2018-03-12 04:08:00 EDT
Could you help to set this bug to on_qa? Thanks
Comment 6 XiuJuan Wang 2018-03-12 21:32:23 EDT
Move this bug to verified as the comment #4

Note You need to log in before you can comment on or make changes to this bug.