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

Bug 1748760

Summary:	[ci] GCP Serial dial tcp: lookup api server on 10.142.15.238:53: no such host
Product:	OpenShift Container Platform	Reporter:	Anping Li <anli>
Component:	Test Infrastructure	Assignee:	Steve Kuznetsov <skuznets>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.2.0	CC:	adahiya, aos-bugs, mfojtik
Target Milestone:	---
Target Release:	---
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-09-04 16:31:21 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 Anping Li 2019-09-04 06:51:23 UTC

Description of problem:
https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/canary-openshift-ocp-installer-e2e-gcp-serial-4.2/90


Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-09-03-102130

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Dan Mace 2019-09-04 10:18:52 UTC

The error message implies to me a networking issue local to the node — reassigning to Networking.

Comment 2 Casey Callendrello 2019-09-04 16:23:38 UTC

This very much looks like the internal load balancer was deleted by the reaper during the test run... Definitely not a networking issue.

Get https://api.ci-op-4hks9vc8-03113.origin-ci-int-gce.dev.openshift.com:6443/api/v1/nodes?fieldSelector=spec.unschedulable%3Dfalse&resourceVersion=0: dial tcp: lookup api.ci-op-4hks9vc8-03113.origin-ci-int-gce.dev.openshift.com on 10.142.15.238:53: no such host

That's the error message seen in all the failing tests. Assigning to the CI team - why was this deleted?

Comment 3 Abhinav Dahiya 2019-09-04 16:31:21 UTC


*** This bug has been marked as a duplicate of bug 1744046 ***