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
Status: NEW
Product: OpenShift Container Platform
Classification: Red Hat
Component: Containers (Show other bugs)
3.6.0
Unspecified Unspecified
medium Severity low
: ---
: ---
Assigned To: Mrunal Patel
DeShuai Ma
: Regression
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-17 05:21 EDT by XiuJuan Wang
Modified: 2017-09-18 18:22 EDT (History)
3 users (show)

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


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:
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 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:
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 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.

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