Bug 1636053
| Summary: | "PLEG is not healthy" errors on OpenShift nodes and the node state is seen as NotReady | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | RamaKasturi <knarra> |
| Component: | Containers | Assignee: | Brent Baude <bbaude> |
| Status: | CLOSED WONTFIX | QA Contact: | weiwei jiang <wjiang> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.11.0 | CC: | aos-bugs, chunzhan, cstark, jokerman, mmccomas, ngalvin, pkundra, sponnaga |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | 3.11.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-05-20 14:21:41 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
RamaKasturi
2018-10-04 10:54:48 UTC
sosreports from all the nodes are present in the link below. http://rhsqe-repo.lab.eng.blr.redhat.com/cns/bugs/BZ-1636053 @seth @rama - Is this blocker for 3.11? We need to close 3.11 ASAP. So checking on this. Can you update the defect and send me a note. PLEG is not healthy: pleg was last seen active 52h35m10.665630586s ago; threshold is 3m0s indicates that the runtime is either down or has been non-responsive for a long time. I'm on a bandwidth restricted connection atm. Can you confirm that a "docker run" from the command line is successful. If this can't be done, I'll send it to Containers. Hello, I currently do not have the setup to do "docker run". But after restarting docker on that particular node which was down, node has come up and everything started working fine in my case. I have hit this issue only once and yesterday i did ran the same test which caused this issue, but did not find this again. Thanks kasturi Seems like this was a runtime issue (either not started or locked up). I'll move to Container and close since it seems like it might have been an isolated thing. If you reopen, it'll be in the correct component. Our client will migrate the very critical app to OpenShift 3.11 in middle of this Month , we often encounter this issue, Can we fix this issue as soon as possible. Is there another way to fix this issue without service restart, Please refer to https://access.redhat.com/solutions/3258011 Actually, I also find the issue from Kubernetes community: https://github.com/kubernetes/kubernetes/issues/45419. docker version 1.13.1-103 ocp v3.11.141 RHEL7.6 kernel: 3.10-1062.1.1 No root cause or reproducer determined. |