Bug 1889900
Summary: | OpenShift API stops responding during upgrade | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Fabian von Feilitzsch <fabian> |
Component: | openshift-apiserver | Assignee: | Luis Sanchez <sanchezl> |
Status: | CLOSED DUPLICATE | QA Contact: | Xingxing Xia <xxia> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 4.7 | CC: | aos-bugs, bruce_link, jsafrane, mf.flip, mfojtik, wking, wlewis |
Target Milestone: | --- | Flags: | mfojtik:
needinfo?
|
Target Release: | 4.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | trt LifecycleStale | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-01-27 17:54:18 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
Fabian von Feilitzsch
2020-10-20 20:54:04 UTC
Bumping severity, OCP 4.7 releases are not promoted due to this bug. This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that. During the upgrade from OKD 4.5 to 4.6, I ran into a similar problem. Description After cluster upgrade I cant open openshift console. OAuth service not working. In events present message "APIService check reporeted "oauth.openshift.io.v1" is not ready: 503" Some commands stop working: $ ./oc get route --all-namespaces Error from server (ServiceUnavailable): the server is currently unable to handle the request (get routes.route.openshift.io) Some operators in DEGRADED state $ ./oc get co | awk '$5 == "True" || $5 == "DEGRADED"' NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE authentication 4.6.0-0.okd-2020-12-12-135354 False True True 24h console 4.6.0-0.okd-2020-12-12-135354 False False True 23h image-registry 4.6.0-0.okd-2020-12-12-135354 True False True 20h monitoring Version 4.5.0-0.okd-2020-10-15-235428 upgrade to 4.6.0-0.okd-2020-11-27-200126 4.6.0-0.okd-2020-12-12-135354 The problem is described in more detail here https://github.com/openshift/okd/issues/395 I can provide any additional information if required. The LifecycleStale keyword was removed because the bug got commented on recently. The bug assignee was notified. We are having same issue as mf.flip. As above, $ oc get route --all-namespaces Error from server (ServiceUnavailable): the server is currently unable to handle the request (get routes.route.openshift.io) $ oc get co | awk '$5 == "True" || $5 == "DEGRADED"' NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE authentication 4.6.0-0.okd-2020-12-12-135354 False True True 19h console 4.6.0-0.okd-2020-12-12-135354 False False True 13h image-registry 4.6.0-0.okd-2020-12-12-135354 False True True 18h monitoring 4.6.0-0.okd-2020-12-12-135354 False True True 19h Looking at unavailable operators adds: openshift-apiserver 4.6.0-0.okd-2020-12-12-135354 False False False 19h operator-lifecycle-manager-packageserver 4.6.0-0.okd-2020-12-12-135354 False True False 13s Further information, including must-gather report is available. This bug hasn't had any activity in the last 30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale" and decreasing the severity/priority. If you have further information on the current state of the bug, please update it, otherwise this bug can be closed in about 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. Additionally, you can add LifecycleFrozen into Keywords if you think this bug should never be marked as stale. Please consult with bug assignee before you do that. *** This bug has been marked as a duplicate of bug 1912820 *** |