Bug 1835146
Summary: | [BM IPI] etcd containers not started on master after restoring to previous state | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Yurii Prokulevych <yprokule> | |
Component: | Etcd | Assignee: | Sam Batschelet <sbatsche> | |
Status: | CLOSED ERRATA | QA Contact: | ge liu <geliu> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 4.4 | CC: | sasha, skolicha | |
Target Milestone: | --- | |||
Target Release: | 4.5.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause: restore process was stopping all static pods but only restarting etcd, api-server, api-scheduler and controller-manager. Bare metal has network pods which are stopped, but not restarted.
Consequence: Without the network pods restarted, the kubelets cannot communicate and the cluster doesn't come up.
Fix: Only stop the 4 pods which are affected by restore.
Result: The cluster comes up fine.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1836270 (view as bug list) | Environment: | ||
Last Closed: | 2020-07-13 17:38:07 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: | 1836270 |
Description
Yurii Prokulevych
2020-05-13 08:53:52 UTC
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, 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/RHBA-2020:2409 |