Bug 1775057
Summary: | [MSTR-485] Cluster is abnormal after etcd backup/restore when the backup is conducted during etcd encryption is migrating | ||||||
---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Xingxing Xia <xxia> | ||||
Component: | Networking | Assignee: | Andrew McDermott <amcdermo> | ||||
Networking sub component: | router | QA Contact: | Xingxing Xia <xxia> | ||||
Status: | CLOSED ERRATA | Docs Contact: | |||||
Severity: | high | ||||||
Priority: | medium | CC: | aos-bugs, bbennett, geliu, hongli, mfojtik, sttts, xxia | ||||
Version: | 4.3.0 | Keywords: | UpcomingSprint | ||||
Target Milestone: | --- | ||||||
Target Release: | 4.7.0 | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | |||||||
: | 1776811 (view as bug list) | Environment: | |||||
Last Closed: | 2021-02-24 15:10:48 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1776811 | ||||||
Attachments: |
|
Description
Xingxing Xia
2019-11-21 11:50:48 UTC
Created attachment 1638414 [details] Details of the abnormal cluster after backup and restore Env kubeconfig http://file.rdu.redhat.com/~xxia/env-for-bug-1775057.kubeconfig . The env will be preserved for Dev debugging for 1 ~ 2 day(s). @xxia, it's kube-apiserver component, your cake! ^_^ Moving like its clone bug did. https://bugzilla.redhat.com/show_bug.cgi?id=1776811#c29 ~ 30 has the known router pod restart issue. That is not fixed yet. Guess 4.4 same, so assigned back. I tried the backup procedure but ran into: Not a blocker for 4.4 and waiting on: - https://bugzilla.redhat.com/show_bug.cgi?id=1788895 - https://bugzilla.redhat.com/show_bug.cgi?id=1807447 Moving to 4.5. Moved to 4.6 until we can work out whether the workaround is still acceptable or whether worker nodes where the router runs need to be either rebooted or the router should be scale down/up to pick up the new endpoints. I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint. I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint. I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint. Target reset from 4.6 to 4.7 while investigation is either ongoing or not yet started. Will be considered for earlier release versions when diagnosed and resolved. I’m adding UpcomingSprint, because I was occupied by fixing bugs with higher priority/severity, developing new features with higher priority, or developing new features to improve stability at a macro level. I will revisit this bug next sprint. Tagging with UpcomingSprint while investigation is either ongoing or pending. Will be considered for earlier release versions when diagnosed and resolved. Tagging with UpcomingSprint while investigation is either ongoing or pending. Will be considered for earlier release versions when diagnosed and resolved. Tagging with UpcomingSprint while investigation is either ongoing or pending. Will be considered for earlier release versions when diagnosed and resolved. Andrew McDermott, 4.6 regular tests didn't hit it. So moving to VERIFIED. Thanks for tracking it. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:5633 |