Bug 1731243

Summary: console: error contacting auth provider, no route to host in proxied cluster
Product: OpenShift Container Platform Reporter: Seth Jennings <sjenning>
Component: Dev ConsoleAssignee: cvogt
Status: CLOSED NOTABUG QA Contact: Ruchir Garg <rgarg>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: aos-bugs, nmukherj
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-07-18 21:15:37 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 Seth Jennings 2019-07-18 18:07:26 UTC
console tries to connect to oauth on the external router

$ oc get event | grep OperatorStatusChanged
38m         Normal   OperatorStatusChanged    deployment/console-operator              Status for clusteroperator/console changed: Upgradeable changed from Unknown to True ("")
38m         Normal   OperatorStatusChanged    deployment/console-operator              Status for clusteroperator/console changed: Degraded changed from Unknown to False ("")
38m         Normal   OperatorStatusChanged    deployment/console-operator              Status for clusteroperator/console changed: Degraded message changed from "" to "Degraded: waiting on route host",Progressing changed from Unknown to True ("Progressing: waiting on route host"),Available changed from Unknown to True ("Available: As expected")
37m         Normal   OperatorStatusChanged    deployment/console-operator              Status for clusteroperator/console changed: Degraded message changed from "Degraded: waiting on route host" to "Degraded: As expected",Progressing message changed from "Progressing: waiting on route host" to "Progressing: Changes made during sync updates, additional sync expected.",Available changed from True to False ("Available: 0 pods available for console deployment")
37m         Normal   OperatorStatusChanged    deployment/console-operator              Status for clusteroperator/console changed: Progressing message changed from "Progressing: Changes made during sync updates, additional sync expected." to "Progressing: Working toward version 4.2.0-0.ci-2019-07-18-124119"

$ oc logs console-operator-76cb5f7486-5p8fk | grep route
E0718 17:26:52.519579       1 sync_v400.go:383] "route": waiting on route host
E0718 17:26:52.596694       1 controller.go:129] {Console Console} failed with: waiting on route host

$ oc logs console-5fdbcf8947-k9c9q
2019/07/18 17:59:16 cmd/main: cookies are secure!
2019/07/18 17:59:19 auth: error contacting auth provider (retrying in 10s): request to OAuth issuer endpoint https://oauth-openshift.apps.lab.variantweb.net/oauth/token failed: Head https://oauth-openshift.apps.lab.variantweb.net: dial tcp 10.42.10.202:443: connect: no route to host

The pods/nodes have no route to the external router address in a cluster behind a proxy.

Comment 1 Seth Jennings 2019-07-18 21:15:37 UTC
After talking to Clayton, I think we are just going to make it a requirement that the router wildcard DNS entry resolve to an address reachable from behind the proxy.