-
Notifications
You must be signed in to change notification settings - Fork 298
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
Upgrade to 4.11.0-0.okd-2023-01-14-152430 fails with OAuthServerRouteEndpointAccessibleControllerAvailable 172.30.0.10:53: server misbehaving dial tcp #1491
Comments
DNS appears to be working fine inside and outside the cluster.
sh-4.4# dig oauth-openshift.apps.ocp.ois.run @172.30.0.10
; <<>> DiG 9.11.36-RedHat-9.11.36-3.el8 <<>> oauth-openshift.apps.ocp.ois.run @172.30.0.10
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50328
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
; COOKIE: dc336dd7780f0cf0 (echoed)
;; QUESTION SECTION:
;oauth-openshift.apps.ocp.ois.run. IN A
;; ANSWER SECTION:
oauth-openshift.apps.ocp.ois.run. 263 IN CNAME ocp.ois.run.
ocp.ois.run. 263 IN A 65.102.23.41
;; Query time: 3 msec
;; SERVER: 172.30.0.10#53(172.30.0.10)
;; WHEN: Sat Feb 04 19:48:03 UTC 2023
;; MSG SIZE rcvd: 157 |
From within the authentication operator pod DNS isn't working:
|
Restarted the openshift-authentication-operator deployment. DNS started working and the upgrade started progressing again.
Upgrade started progressing again:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
`oc get co`
Version
UPI
How reproducible
Log bundle
The text was updated successfully, but these errors were encountered: