Skip to content

Extended test: Clusterup: dial tcp: lookup: server misbehaving #17548

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
juanvallejo opened this issue Nov 30, 2017 · 4 comments
Closed

Extended test: Clusterup: dial tcp: lookup: server misbehaving #17548

juanvallejo opened this issue Nov 30, 2017 · 4 comments
Assignees
Labels
component/cluster-up kind/bug Categorizes issue or PR as related to a bug. priority/P2

Comments

@juanvallejo
Copy link
Contributor

FAILURE after 29.679s: test/extended/clusterup.sh:118: executing 'oc cluster up --public-hostname=myserver.127.0.0.1.nip.io --version=213f9a8' expecting success: the command returned the wrong error code
Standard output from the command:
Starting OpenShift using openshift/origin:213f9a8 ...
-- Checking OpenShift client ... OK
-- Checking Docker client ... OK
-- Checking Docker version ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:213f9a8 image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... OK
-- Checking type of volume mount ... 
   Using nsenter mounter for OpenShift volumes
-- Creating host directories ... OK
-- Finding server IP ... 
   Using 127.0.0.1 as the server IP
-- Starting OpenShift container ... 
   Creating initial OpenShift configuration
   Starting OpenShift using container 'origin'
   Waiting for API server to start listening
   OpenShift server started
-- Adding default OAuthClient redirect URIs ... OK
-- Installing registry ... 
   scc "privileged" added to: ["system:serviceaccount:default:registry"]
-- Installing router ... OK
-- Importing image streams ... OK
-- Importing templates ... OK
-- Login to server ... 
   error: dial tcp: lookup myserver.127.0.0.1.nip.io on 172.18.0.2:53: server misbehaving - verify you have provided the correct host and port and that the server is currently running.
FAIL
   Error: dial tcp: lookup myserver.127.0.0.1.nip.io on 172.18.0.2:53: server misbehaving

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17357/test_pull_request_origin_extended_clusterup/186/

@mfojtik
Copy link
Contributor

mfojtik commented Dec 4, 2017

I think I heard that nip.io is dead, maybe we should switch to a new provider?

@pweil- pweil- added component/cluster-up kind/bug Categorizes issue or PR as related to a bug. priority/P2 labels Dec 4, 2017
@csrwng
Copy link
Contributor

csrwng commented Dec 11, 2017

nip.io is working now, but yes we should look for an alternative that doesn't force us to depend on them.

@csrwng
Copy link
Contributor

csrwng commented Dec 11, 2017

/assign @mfojtik

@bparees
Copy link
Contributor

bparees commented Dec 12, 2017

this is working again and we're not going to be the ones to drive a replacement for nip.io

@bparees bparees closed this as completed Dec 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/cluster-up kind/bug Categorizes issue or PR as related to a bug. priority/P2
Projects
None yet
Development

No branches or pull requests

5 participants