Bug 1720174
Summary: | No pod failover when multiple nodes are NotReady | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Sergio G. <sgarciam> | |
Component: | Node | Assignee: | Ryan Phillips <rphillips> | |
Status: | CLOSED ERRATA | QA Contact: | Weinan Liu <weinliu> | |
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | 3.11.0 | CC: | acavalla, akaiser, aos-bugs, asolanas, bfurtado, clpereir, gblomqui, jokerman, mfojtik, mmccomas, mnunes, openshift-bugs-escalate, palonsor, pweil, rphillips, rpuccini, rsunog, schoudha, sjenning, skolicha, tnozicka, xtian | |
Target Milestone: | --- | |||
Target Release: | 3.11.z | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | If docs needed, set a value | ||
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1752894 1753995 (view as bug list) | Environment: | ||
Last Closed: | 2019-10-18 01:34:36 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: | 1752894, 1753995 |
Description
Sergio G.
2019-06-13 10:14:45 UTC
I tend to think that this is related with the fact that the cluster is spread but I can't find a reason why due to the very low latency and the fact that no masters have been turned off during the test so etcd and master-api is okay. If you need anything else please let me know and I'll get it from customer. *** Bug 1722288 has been marked as a duplicate of this bug. *** While going through the logs, I saw the new pods failed to be schedule. It's a slightly different issue, but if you could post all the events for the cluster (for all namespaces), that would help. For whatever it's worth, the initial case which originated this bugzilla is no longer being affected. Customer replaced baremetal servers to host the master servers with virtual machines with the same hardware requirements, and the issue is gone. It may still related to networking if the baremetal servers are differently connected than the virtual machines. 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-2019:3139 |